From: | François Beausoleil <francois(at)teksol(dot)info> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: What could cause a temp table to disappear? |
Date: | 2013-02-27 23:57:56 |
Message-ID: | C8D61813-D73D-40B9-AD2E-80B7740A81FE@teksol.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Le 2013-02-27 à 16:59, Tom Lane a écrit :
> Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
>> On 02/27/2013 01:48 PM, François Beausoleil wrote:
>>> Le 2013-02-27 à 16:45, Adrian Klaver a écrit :
>>>> Also what client/library are you using to connect with?
>
>>> I use Ruby & Sequel. Sequel is a very thin library over straight SQL.
>
>> Everything else is the same? It is acting like something is closing a
>> session on you. Could there be a connection pooler in the mix?
>
> Or just closing a transaction --- note the ON COMMIT DROP. I'm thinking
> something in the client-side stack is doing something you don't expect.
> Suggest turning on server-side logging (log_statement = all, maybe
> log_connections too) rather than trusting this client-side log to be
> telling the whole truth.
Ok, as you suspected, there are multiple connections and the wrong connection was used to execute the wrong queries. I haven't fully found the root cause, but I know where to look.
Thanks for your help!
François
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Hanks | 2013-02-28 02:22:00 | Poor performance when using a window function in a view |
Previous Message | Tom Lane | 2013-02-27 21:59:45 | Re: What could cause a temp table to disappear? |