From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | François Beausoleil <francois(at)teksol(dot)info> |
Cc: | Forums postgresql <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: What could cause a temp table to disappear? |
Date: | 2013-02-27 21:54:05 |
Message-ID: | 512E807D.3080408@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 02/27/2013 01:48 PM, François Beausoleil wrote:
>
> Le 2013-02-27 à 16:45, Adrian Klaver a écrit :
>
>> On 02/27/2013 01:19 PM, François Beausoleil wrote:
>>
>>>
>>> Any hints?
>>
>> See in line notes below.
>> Also what client/library are you using to connect with?
>
> I use Ruby & Sequel. Sequel is a very thin library over straight SQL.
>
>
> This is the production log, and it's the exact same in dev. The data I'm
> putting in the tables is authoritative, except for airings, which may or
> may not already exist in the database. In dev, the INSERT INTO airings
> SELECT * FROM airings_import WHERE NOT EXISTS(...) statement runs to
> completion. That's why I'm puzzled.
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?
>
> Bye,
> François
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2013-02-27 21:59:45 | Re: What could cause a temp table to disappear? |
Previous Message | François Beausoleil | 2013-02-27 21:48:35 | Re: What could cause a temp table to disappear? |