Re: [GENERAL] shared memory/max_locks_per_transaction error

2008-03-17 Thread Kynn Jones
Tom, Alvaro: Thank you much for the clarification. It's "back to the drawing board" for me! Kynn On Mon, Mar 17, 2008 at 10:55 AM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Kynn Jones" <[EMAIL PROTECTED]> writes: > > I'm leaning towards the re-design option, primarily because I really > don't > >

Re: [GENERAL] shared memory/max_locks_per_transaction error

2008-03-17 Thread Erik Jones
On Mar 17, 2008, at 9:55 AM, Tom Lane wrote: "Kynn Jones" <[EMAIL PROTECTED]> writes: I'm leaning towards the re-design option, primarily because I really don't really understand the consequences of cranking up max_locks_per_transaction. E.g. Why is its default value 2^6, instead of, say, 2

Re: [GENERAL] shared memory/max_locks_per_transaction error

2008-03-17 Thread Tom Lane
"Kynn Jones" <[EMAIL PROTECTED]> writes: > I'm leaning towards the re-design option, primarily because I really don't > really understand the consequences of cranking up max_locks_per_transaction. > E.g. Why is its default value 2^6, instead of, say, 2^15? In fact, why is > there a ceiling on the

Re: [GENERAL] shared memory/max_locks_per_transaction error

2008-03-17 Thread Alvaro Herrera
Kynn Jones escribió: > I'm leaning towards the re-design option, primarily because I really don't > really understand the consequences of cranking up max_locks_per_transaction. > E.g. Why is its default value 2^6, instead of, say, 2^15? It's because it (partly) defines how much shared memory the

Re: [GENERAL] shared memory/max_locks_per_transaction error

2008-03-17 Thread Kynn Jones
On Fri, Mar 14, 2008 at 7:12 PM, Tom Lane <[EMAIL PROTECTED]> wrote: > "Kynn Jones" <[EMAIL PROTECTED]> writes: > > Initially I didn't know what our max_locks_per_transaction was (nor even > a > > typical value for it), but in light of the procedure's failure after > 3500 > > iterations, I figured

Re: [GENERAL] shared memory/max_locks_per_transaction error

2008-03-14 Thread Tom Lane
"Kynn Jones" <[EMAIL PROTECTED]> writes: > Initially I didn't know what our max_locks_per_transaction was (nor even a > typical value for it), but in light of the procedure's failure after 3500 > iterations, I figured that it was 3500 or so. In fact ours is only 64 (the > default), so I'm now thor

[GENERAL] shared memory/max_locks_per_transaction error

2008-03-14 Thread Kynn Jones
I've written a PL/pgSQL function that is supposed to create a whole bunch (~4000) tables: CREATE OR REPLACE FUNCTION create_tables () RETURNS void AS $$ DECLARE _s RECORD; _t TEXT; BEGIN DROP TABLE IF EXISTS base CASCADE; CREATE TABLE base ( /* omit lengthy definition */ ); FOR _s IN SEL