Horton
Menu

Re: Largeobject Access Controls (r2460)

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "KaiGai Kohei" <kaigai@kaigai.gr.jp>, "Greg Smith" <greg@2ndquadrant.com>, "KaiGai Kohei" <kaigai@ak.jp.nec.com>, "Robert Haas" <robertmhaas@gmail.com>, "Takahiro Itagaki" <itagaki.takahiro@oss.ntt.co.jp>, pgsql-hackers@postgresql.org, "Jaime Casanova" <jcasanov@systemguards.com.ec>
Date: 2010-01-24T17:53:35Z
Lists: pgsql-hackers 
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
> I'm afraid pg_dump didn't get very far with this before:
 
> pg_dump: WARNING:  out of shared memory
> pg_dump: SQL command failed
 
> Given how fast it happened, I suspect that it was 2672 tables into
> the dump, versus 26% of the way through 5.5 million tables.

Yeah, I didn't think about that.  You'd have to bump
max_locks_per_transaction up awfully far to get to where pg_dump
could dump millions of tables, because it wants to lock each one.

It might be better to try a test case with lighter-weight objects,
say 5 million simple functions.

			regards, tom lane