Prev: Remaining Streaming Replication Open Items
Next: pgsql: Check compulsory parameters in recovery.conf in standby_mode, per
From: "David E. Wheeler" on 6 Apr 2010 15:53
On Apr 6, 2010, at 12:50 PM, Tom Lane wrote:

> I hadn't, but since you mention it: 100000 iterations take about 7.5sec
> with non-assert CVS HEAD and 15sec with asserts, on a 2008 Macbook Pro.
> Color me still confused.

Well it's not just pings that the bricolage tests were running, of course.

Josh, might you have got the numbers wrong when trying to match up query runtimes to their queries in the CSVLOG output? That might explain it. Most of the queries were BINDs.

Best,

David



--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Pavel Stehule on 6 Apr 2010 15:55
2010/4/6 Tom Lane <tgl(a)sss.pgh.pa.us>:
> "David E. Wheeler" <david(a)kineticode.com> writes:
>> On Apr 6, 2010, at 11:15 AM, Tom Lane wrote:
>>> Huh.  I'm still curious, because in my test the overhead of those
>>> options seemed to be about 3x.  So there's still something considerably
>>> different between what you did and what I did.
>
>> Are you doing this on a Mac?
>
> I hadn't, but since you mention it: 100000 iterations take about 7.5sec
> with non-assert CVS HEAD and 15sec with asserts, on a 2008 Macbook Pro.
> Color me still confused.

it is little bit offtopic. Can we add info about assertation to
version() output?

like


postgres=# select version();
version

────────────────────────────────────────────────────────────────────────────────
───────────────────────────────
PostgreSQL 9.0alpha4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.4.3 2010
0127 (Red Hat 4.4.3-4), 32-bit >>> with enabled assertation <<<<
(1 row)

Regards
Pavel Stehule
>
>                        regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
From: Tom Lane on 6 Apr 2010 15:58
Pavel Stehule <pavel.stehule(a)gmail.com> writes:
> it is little bit offtopic. Can we add info about assertation to
> version() output?

Greg has the right idea: show debug_assertions.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Josh Berkus on 6 Apr 2010 16:10

> Josh, might you have got the numbers wrong when trying to match up query runtimes to their queries in the CSVLOG output? That might explain it. Most of the queries were BINDs.

I swept up some DEALLOCATEs by acccident, but those don't appreciably
affect the final numbers.

--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

From: Merlin Moncure on 6 Apr 2010 16:13
On Tue, Apr 6, 2010 at 3:58 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> Pavel Stehule <pavel.stehule(a)gmail.com> writes:
>> it is little bit offtopic. Can we add info about assertation to
>> version() output?
>
> Greg has the right idea: show debug_assertions.

why not the entire set of configure options?

merlin

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: Remaining Streaming Replication Open Items
Next: pgsql: Check compulsory parameters in recovery.conf in standby_mode, per