| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, 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-15 01:04:57 |
| Message-ID: | 20319.1471223097@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2016-08-07 14:46:06 -0400, Tom Lane wrote:
>> 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.
> That seems a bit too defeatist.
Huh? I didn't say we shouldn't work on the problem --- I just think that
this particular approach isn't good. Which you seemed to agree with.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-08-15 01:08:52 | Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) |
| Previous Message | Andres Freund | 2016-08-15 00:57:55 | Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) |