| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, agoldshuv(at)greenplum(dot)com |
| Subject: | Re: [PATCHES] WAL bypass for CTAS |
| Date: | 2005-06-05 04:17:23 |
| Message-ID: | 696.1117945043@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I suppose no one would like adding an option to turn off locking during
> COPY, so the non-WAL logging would become the default?
When and if we add LOCK or some equivalent option to COPY, I'm sure
we'll change pg_dump to specify that option in its output. But trying
to get that behavior by default for existing dumps seems to me to be
far more dangerous than it's worth. Not every performance improvement
has to automatically apply to existing dumps...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-05 04:45:32 | Re: [HACKERS] WAL: O_DIRECT and multipage-writer (+ memory |
| Previous Message | Tom Lane | 2005-06-05 04:11:34 | Re: regexp_replace |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-05 04:45:32 | Re: [HACKERS] WAL: O_DIRECT and multipage-writer (+ memory |
| Previous Message | Tom Lane | 2005-06-05 04:11:34 | Re: regexp_replace |