Re: [PERFORM] Drop Tables Very Slow in Postgresql 7.2.1

2004-03-14 Thread Andrew Sullivan
On Wed, Mar 10, 2004 at 12:33:01PM +0530, Maneesha Nunes wrote: Hello there !!! I am using postgresql7.2.1 as the backend for an E.R.P system running on Linux Redhat 7.2(Enigma) You should upgrade, to at the _very least_ the last release of 7.2. There were bugs in earlier releases fixed

Re: [PERFORM] [ADMIN] syslog slowing the database?

2004-03-14 Thread Andrew Sullivan
On Thu, Mar 11, 2004 at 09:34:54AM +0800, Christopher Kings-Lynne wrote: You could also consider not using syslog at all: let the postmaster output to its stderr, and pipe that into a log-rotation program. Not an option I'm afraid. PostgreSQL just jams and stops logging after the first

[PERFORM] Large CASE-statement is pretty slow?

2004-03-14 Thread Arjen van der Meijden
Hi list, I was more or less toying with an idea for a project I have, which includes renumbering a primary key (don't ask, it's necessary :/ ) Anyway, I was looking into the usefullness of a INSERT INTO newtable SELECT field, field, CASE pkey WHEN x1 THEN y1 WHEN x2 THEN y2 etc END FROM

Re: [PERFORM] Scaling further up

2004-03-14 Thread Aaron Werman
Sorry about not chiming in before - I've been too swamped to think. I agree with most of the points, but a lot of these posts are interesting and seem to describe systems from an SA perspective to my DBA-centric view. - Original Message - From: Marty Scholes [EMAIL PROTECTED] To: [EMAIL

[PERFORM] Deadlocks...

2004-03-14 Thread postgres
Hi, i have 2 Functions, one ist called by page visitors (something about 2,000 times / 1 hour) and the other just by the admin (let say 1 time per hour or per login) i often get a deadlock error after calling the admin function yes they try to access the same table somewhere in the function code.