From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steve Singer <ssinger@ca.afilias.info>
Cc: PostgreSQL-development Hackers <pgsql-hackers@postgresql.org>
Subject: Re: skip WAL on COPY patch
Date: Tue, 23 Aug 2011 15:05:20 -0400
Message-ID: <1739.1314126320@sss.pgh.pa.us> (raw)
In-Reply-To: <4E53E7D5.6030808@ca.afilias.info>
References: <4E53E7D5.6030808@ca.afilias.info>
Steve Singer <ssinger@ca.afilias.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, ssinger@ca.afilias.info
Subject: Re: skip WAL on COPY patch
In-Reply-To: <1739.1314126320@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox