Re: [PERFORM] Background fsck

Στις Friday 08 April 2011 08:55:51 ο/η Ireneusz Pluta έγραψε: Achilleas Mantzios wrote: In anyway, having FreeBSD to fsck, (background or not) should not happen. And the problem becomes bigger when cheap SATA drives will cheat about their write cache being flushed to the disk. So

Re: [PERFORM] Background fsck

my life a little with background checks. -- Achilleas Mantzios -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] Postgres Performance Tuning

up above? Have you run any of those? -- Achilleas Mantzios -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] pg9.0.3 explain analyze running very slow compared to a different box with much less configuration

this issue, any help would be in great assistance. Thanks Deepak -- Achilleas Mantzios -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] pg9.0.3 explain analyze running very slow compared to a different box with much less configuration

Στις Thursday 24 March 2011 13:39:19 ο/η Marti Raudsepp έγραψε: On Thu, Mar 24, 2011 at 11:11, Achilleas Mantzios ach...@matrix.gatewaynet.com wrote: My problem had to do with the speed of gettimeofday. You might want to do some special setting regarding your box's way of reading time

Re: [PERFORM] Talking about optimizer, my long dream

to have a recording of *that* phone call. -- Greg Smith 2ndQuadrant USg...@2ndquadrant.com Baltimore, MD PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us PostgreSQL 9.0 High Performance: http://www.2ndQuadrant.com/books -- Achilleas Mantzios -- Sent via

Re: [PERFORM] NOT IN substantially slower in 9.0.2 than 8.3.13 - NOT EXISTS runs fast in both 8.3.13 and 9.0.2

) = 1 - (probability that all values in the inner relation are equal to the value of the outer tuple) Anyways, glad to see smth came out of this. Thx regards, tom lane -- Achilleas Mantzios -- Sent via pgsql-performance mailing list (pgsql-performance

Re: [PERFORM] NOT IN substantially slower in 9.0.2 than 8.3.13 - NOT EXISTS runs fast in both 8.3.13 and 9.0.2

) 329-5251 www.vmsinfo.com -- Achilleas Mantzios -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance

Re: [PERFORM] NOT IN substantially slower in 9.0.2 than 8.3.13 - NOT EXISTS runs fast in both 8.3.13 and 9.0.2

Στις Wednesday 19 January 2011 19:26:56 ο/η Tom Lane έγραψε: Achilleas Mantzios ach...@matrix.gatewaynet.com writes: Anyway, i will repost the EXPLAIN plans by copying pasting the query, without the analyze part. Please show EXPLAIN ANALYZE, not just EXPLAIN, results. When complaining

[PERFORM] NOT IN substantially slower in 9.0.2 than 8.3.13 - NOT EXISTS runs fast in both 8.3.13 and 9.0.2

FBSD_TEST (while running a bigger database, a recent dump from LINUX_PROD) to be actually slower than LINUX_PROD. From the whole set of the tests involved, it seems like the NOT IN version of the query runs slow in any postgresql 9.0.2 tested. -- Achilleas Mantzios -- Sent via pgsql

[PERFORM] syslog performance when logging big statements

to better tune pgsql/syslog in order to work more efficiently in cases like that? I know it is a corner case, however i thought i should post my experiences. Thanx -- Achilleas Mantzios -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription

Re: [PERFORM] syslog performance when logging big statements

Στις Tuesday 08 July 2008 17:35:16 ο/η Tom Lane έγραψε: Achilleas Mantzios [EMAIL PROTECTED] writes: In this case, the INSERT *needs* 20 minutes to return. This is because the logging through syslog seems to severely slow the system. If instead, i use stderr, even with logging_collector