From: | Steve Crawford <scrawford(at)pinpointresearch(dot)com> |
---|---|
To: | Phoenix Kiula <phoenix(dot)kiula(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: URGENT: temporary table not recognized? |
Date: | 2012-01-07 00:16:23 |
Message-ID: | 4F078ED7.9030309@pinpointresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/06/2012 03:12 PM, Phoenix Kiula wrote:
> ...
>> Sounds like you are using statement pooling - every statement can be
>> assigned to a different server connection. You may need transaction pooling
>> or session pooling:
>>
>> http://pgbouncer.projects.postgresql.org/doc/usage.html
>
>
> Thanks Steve. YES! I changed it to transaction pooling and now it works.
>
But Marko is correct. If you were using:
begin;
create temporary...
\copy
commit;
and if your pooler was set to statement then you should have seen an error.
Are you by any chance routing stderr to /dev/null or otherwise hiding
messages? If you are using "psql.....2>/dev/null" then everything would
*look* the same with pooling set to statement or transaction but you
would be blissfully ignorant of the errors.
Cheers,
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Steve Crawford | 2012-01-07 00:44:12 | Re: URGENT: temporary table not recognized? |
Previous Message | Phoenix Kiula | 2012-01-07 00:16:09 | Re: URGENT: temporary table not recognized? |