Re: 1.12.0. bug

Le 29/09/2010 00:28, Guillaume Lelarge a écrit :
> Le 28/09/2010 16:54, Dave Page a écrit :
>> [Please keep the lis CC'd]
>>
>> On Tue, Sep 28, 2010 at 2:47 PM, Little, Douglas
>> <DOUGLAS.LITTLE@orbitz.com>wrote:
>>
>>>  Sorry,  to lazy to retype the version info and not sure if it was beta or
>>> not.
>>>
>>>
>>>
>>> PGadmin env.  Win xp sp3.
>>>
>>> Server:  Greenplum 3.6.6.6 (pg 8.2.13)
>>>
>>> Version string    PostgreSQL 8.2.13 (Greenplum Database 3.3.6.6 build 2) on
>>> x86_64-pc-solaris2.10, compiled by GCC gcc.exe (GCC) 4.1.1 compiled on Jul
>>> 16 2010 18:38:06
>>>
>>>
>>>
>>
>> Oh, Greenplum. I don't have a copy here, but if you can grab the query
>> pgAdmin is trying to run from the logfile (you might need to switch on Query
>> Logging under File->Options->Logging), and figure out what will work on
>> GPDB, I can special-case that in the code for the 1.12.1 build (due to be
>> tagged on Thursday).
>>
> 
> In fact, it's reproducile quite easily;
> 

And now my complete message. I reproduce it on 8.2, with the locks and
prepared transactions reports. I fixed both. And I fix the "SET
log_statement" query too.

Thanks for the report.


-- 
Guillaumehttp://www.postgresql.frhttp://dalibo.com