| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, David Steele <david(at)pgmasters(dot)net> |
| Subject: | Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) |
| Date: | 2016-08-07 18:46:06 |
| Message-ID: | 14212.1470595566@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I think the whole idea of a fast temporary table is that there are no
> catalog entries. If there are no catalog entries, then dependencies
> are not visible. If there ARE catalog entries, to what do they refer?
> Without a pg_class entry for the table, there's no table OID upon
> which to depend.
TBH, I think that the chances of such a design getting committed are
not distinguishable from zero. Tables have to have OIDs; there is just
too much code that assumes that. And I seriously doubt that it will
work (for any large value of "work") without catalog entries.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2016-08-07 19:05:11 | garbage in xml regress test |
| Previous Message | Robert Haas | 2016-08-07 18:35:32 | Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) |