why do we have rd_istemp?
in [PgSql]
|
Prev: improve plpgsql's EXECUTE 'select into' messagewith a hint
Next: bitmap-index-scan faster than seq-scan on full-table-scan (gin index)
From: Bruce Momjian on 31 May 2010 16:03 Tom Lane wrote: > Robert Haas <robertmhaas(a)gmail.com> writes: > > Given "Relation rel", it looks to me like rel->rd_rel->relistemp will > > always give the same answer as rel->rd_istemp. So why have both? > > Might be historical --- relistemp is pretty new. Is this a TODO or something we want to clean up? -- Bruce Momjian <bruce(a)momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. + -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 31 May 2010 16:12
Bruce Momjian <bruce(a)momjian.us> writes: > Tom Lane wrote: >> Robert Haas <robertmhaas(a)gmail.com> writes: >>> Given "Relation rel", it looks to me like rel->rd_rel->relistemp will >>> always give the same answer as rel->rd_istemp. So why have both? >> >> Might be historical --- relistemp is pretty new. > Is this a TODO or something we want to clean up? Doesn't strike me that it's worth the amount of code that would have to change. rd_istemp is known in a lot of places. Replacing it with a double indirection doesn't seem attractive anyway. regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |