On Tue, Nov 27, 2012 at 6:26 PM, Steve Atkins wrote:
>
> On Nov 27, 2012, at 2:04 PM, Mike Blackwell
> wrote:
>
> > I need to delete about 1.5 million records from a table and reload it in
> one transaction. The usual advice when loading with inserts seems to be
> group them into transactions o
We had a problem in the 8.X series with COPY IN - it did not respect any
configured maximums and just kept allocating memory until it could fit the
entire COPY contents down to the \. into RAM. Could there be a similar
issue with COPY OUT?
-
Dan
On Wed, Jun 11, 2014 at 6:02 PM, Timothy Garn
> From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Behalf Of Glyn Astill
> Sent: Tuesday, October 02, 2012 4:21 AM
> To: M. D.; pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] hardware advice
>
>> From: M. D.
>> To: pgsql-performance@postgre
This is a good general discussion of the problem - looks like you could
replace "MySQL" with "PostgreSQL" everywhere without loss of generality:
http://blog.jcole.us/2010/09/28/mysql-swap-insanity-and-the-numa-archite
cture/
Dan
-Original Message-
From: pgsql-performance-ow...@postgresq