Am 22.03.2012 15:48, schrieb Tom Lane:
What PG version are we talking about, and what exactly is the
problematic index?
Index is on (inet, integer, smallint, timestamp w/o timezone), btree
and a primary key.
There was a memory leak in the last-but-one releases for index
operations on inet a
Heiko Wundram writes:
> On a host that I'm currently in the process of migrating, I'm
> experiencing massive memory usage when importing the dump (generated
> using a plain pg_dump without options) using psql. The massive memory
> usage happens when the CREATE INDEX commands are executed,
What
Hey!
On a host that I'm currently in the process of migrating, I'm
experiencing massive memory usage when importing the dump (generated
using a plain pg_dump without options) using psql. The massive memory
usage happens when the CREATE INDEX commands are executed, and for a
table with about 4
