| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> | 
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> | 
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> | 
| Subject: | Re: autovacuum and TOAST tables | 
| Date: | 2008-08-11 22:58:37 | 
| Message-ID: | 10824.1218495517@sss.pgh.pa.us | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> BTW only now I notice that CLUSTER leaves the toast table name in bad
> shape: if you create a table with OID X its TOAST table is named
> pg_toast_X.  If you then cluster this table, a new transient table gets
> created with OID Y; the TOAST table for Y is named pg_toast_Y, and then
> this new TOAST table is used as the new TOAST table for the original
> table X.  So you end up with table OID X having TOAST table pg_toast_Y.
Hmm, we could probably fix that if we made the cluster operation swap
the physical storage of the two toast tables, rather than swapping the
tables altogether.  I agree it's not critical but it could be confusing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-08-11 23:06:41 | Re: autovacuum and TOAST tables | 
| Previous Message | Alvaro Herrera | 2008-08-11 22:42:08 | Re: autovacuum and TOAST tables |