Re: [PERFORM] Lock pileup causes server to stall

2014-11-11 Thread Jesper Krogh
> On 10/11/2014, at 22.40, Alvaro Herrera wrote: > > Josh Berkus wrote: >> All, >> >> pg version: 9.3.5 >> RHEL 6.5 >> 128GB/32 cores >> Configured with shared_buffers=16GB >> Java/Tomcat/JDBC application >> >> Server has an issue that whenever we get lock waits (transaction lock >> waits, usu

Re: [PERFORM] Lock pileup causes server to stall

2014-11-11 Thread Jeff Janes
On Tue, Nov 11, 2014 at 9:11 AM, Josh Berkus wrote: > On 11/10/2014 01:40 PM, Alvaro Herrera wrote: > > Josh Berkus wrote: > >> All, > >> > >> pg version: 9.3.5 > >> RHEL 6.5 > >> 128GB/32 cores > >> Configured with shared_buffers=16GB > >> Java/Tomcat/JDBC application > >> > >> Server has an iss

Re: [PERFORM] Lock pileup causes server to stall

2014-11-11 Thread Josh Berkus
On 11/10/2014 01:40 PM, Alvaro Herrera wrote: > Josh Berkus wrote: >> All, >> >> pg version: 9.3.5 >> RHEL 6.5 >> 128GB/32 cores >> Configured with shared_buffers=16GB >> Java/Tomcat/JDBC application >> >> Server has an issue that whenever we get lock waits (transaction lock >> waits, usually on an

Re: [PERFORM] [GENERAL] trigger Before or After

2014-11-11 Thread Adrian Klaver
On 11/10/2014 10:38 PM, avpro avpro wrote: hi, in the pgsql documentation (http://www.postgresql.org/docs/9.1/static/sql-createtrigger.html) i haven't seen anything referring to: how is affected the data inserted in the new table by a trigger Before Insert compared with a trigger After Insert?

Re: [PERFORM] [GENERAL] trigger Before or After

2014-11-11 Thread Albe Laurenz
avpro avpro wrote: > in the pgsql documentation > (http://www.postgresql.org/docs/9.1/static/sql-createtrigger.html) > > > i haven't seen anything referring to: how is affected the data inserted in > the new table by a trigger > Before Insert compared with a trigger After Insert? and anything re