| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Jacky Leng <lengjianquan(at)163(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Why copy_relation_data only use wal whenWALarchivingis enabled |
| Date: | 2007-10-18 13:52:23 |
| Message-ID: | 22479.1192715543@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> The best I can think of is to rename the obsolete file to
> <relfilenode>.stale, when it's scheduled for deletion at next
> checkpoint, and check for .stale-suffixed files in GetNewRelFileNode,
> and delete them immediately in DropTableSpace.
This is getting too Rube Goldbergian for my tastes. What if we just
make DROP TABLESPACE force a checkpoint before proceeding?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-10-18 13:56:38 | Re: Proposal: generate_iterator functions |
| Previous Message | Tom Lane | 2007-10-18 13:47:37 | Re: ts_rewrite aggregate API seems mighty ugly |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2007-10-18 14:15:00 | Re: Why copy_relation_data only use wal whenWALarchivingis enabled |
| Previous Message | Stefan Schwarzer | 2007-10-18 13:24:17 | Crosstab Problems |