| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steve Singer <ssinger(at)ca(dot)afilias(dot)info> |
| Cc: | PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: skip WAL on COPY patch |
| Date: | 2011-08-23 19:05:20 |
| Message-ID: | 1739.1314126320@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Steve Singer <ssinger(at)ca(dot)afilias(dot)info> writes:
> The attached patch adds an option to the COPY command to skip writing
> WAL when the following conditions are all met:
> 1) The table is empty (zero size on disk)
> 2) The copy command can obtain an access exclusive lock on the table
> with out blocking.
> 3) The WAL isn't needed for replication
Exposing this as a user-visible option seems a seriously bad idea.
We'd have to support that forever. ISTM it ought to be possible to
avoid the exclusive lock ... maybe not with this particular
implementation, but somehow.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-08-23 19:09:34 | Re: Getting rid of pg_pltemplate |
| Previous Message | Tom Lane | 2011-08-23 18:59:18 | Re: text search: restricting the number of parsed words in headline generation |