From: Stephen Frost <sfrost@snowman.net>
To: Markus Schulz <msc@antzsystem.de>
Cc: pgsql-performance@postgresql.org
Subject: Re: BUG: endless lseek(.., SEEK_END) from select queries on x64 builds
Date: Fri, 22 Feb 2013 08:37:23 -0500
Message-ID: <20130222133723.GR16142@tamriel.snowman.net> (raw)
In-Reply-To: <201302220925.26460.msc@antzsystem.de>
References: <201302220925.26460.msc@antzsystem.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Markus,
* Markus Schulz (msc@antzsystem.de) wrote:
> as you can see the query runs fine.
> I can run this query from a bash-psql-while-loop/jdbc-cli-tool
> endless without any problems.
> so far so good.
[...]
> JBoss EAP 5.1.2 with connection pooling and xa-datasource/two-phase-commits
> (transactions on multiple datasources needed)
> *and* *<prepared-statement-cache-size>1000</prepared-statement-cache-size>*
>
> i can run the query four times with good performance and after that postgresql
> starts with the strange lseek() behavior.
It sounds like your bash script and JBoss are doing something different.
Would it be possible for you to turn on log_statements = 'all' in PG,
see what's different, and then update the bash/psql script to do exactly
what JBoss does, and see if you can reproduce it that way?
It certainly looks like a PG bug, but it'd be a lot easier to debug with
a simple, well-defined test case which shows the failure.
Thanks!
Stephen
Attachments:
signature.asc (application/pgp-signature, 197B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: sfrost@snowman.net, msc@antzsystem.de
Subject: Re: BUG: endless lseek(.., SEEK_END) from select queries on x64 builds
In-Reply-To: <20130222133723.GR16142@tamriel.snowman.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox