| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <simon(at)2ndQuadrant(dot)com>,<heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | <andrew(at)dunslane(dot)net>,<pgsql(at)j-davis(dot)com>, <bruce(at)momjian(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Reduce WAL logging of INSERT SELECT |
| Date: | 2011-08-06 16:21:41 |
| Message-ID: | 4E3D23C5020000250003FBD8@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
> On 06.08.2011 13:13, Simon Riggs wrote:
>> I think we should remove the COPY optimisation because of this and
>> definitely not extend INSERT SELECT to perform it automatically.
>
> It can be very helpful when loading a lot of data, so I'm not in
> favor of removing it altogether.
Yeah, it can currently help a lot. Of course, if WAL-logging could
in any way facilitate hint bit and frozen xmin setting during bulk
loads, I'm sure the WAL-logged version would win easily.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-06 16:23:38 | Re: Reduce WAL logging of INSERT SELECT |
| Previous Message | Jaime Casanova | 2011-08-06 16:13:27 | Re: Reduce WAL logging of INSERT SELECT |