Обсуждение: 1.12.0. bug

Поиск
Список
Период
Сортировка

1.12.0. bug

От
"Little, Douglas"
Дата:

In the server status screen.   If in the LOCKS section,  I click on the user column header I get this error.

All of the other columns seem to be working correctly.

I do not  have superuser credentials.

 

 

 

Thanks for a major upgrade.   You guys have put a lot into it.  Just a bit more.

 

Thanks

 

Doug Little

 

Sr. Data Warehouse Architect | Enterprise Data Management | Orbitz Worldwide

500 W. Madison, Suite 1000  Chicago IL 60661| Office 312.260.2588 | Fax 312.894.5164 | Cell 847-997-5741

Douglas.Little@orbitz.com

 cid:image001.jpg@01CABEC8.D4980670  orbitz.com | ebookers.com | hotelclub.com | cheaptickets.com | ratestogo.com | asiahotels.com

 

Re: 1.12.0. bug

От
Dave Page
Дата:
Hi

On Tue, Sep 28, 2010 at 1:31 PM, Little, Douglas <DOUGLAS.LITTLE@orbitz.com> wrote:

In the server status screen.   If in the LOCKS section,  I click on the user column header I get this error.

All of the other columns seem to be working correctly.

I do not  have superuser credentials.

 


I thought that was fixed in one of the betas - and I can't reproduce the error here with the release version. Are you definitely running the GA build, and not an RC or beta of 1.12.0? 


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

Re: 1.12.0. bug

От
Dave Page
Дата:
[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).


--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise Postgres Company

Re: 1.12.0. bug

От
Guillaume Lelarge
Дата:
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;


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


Re: 1.12.0. bug

От
Guillaume Lelarge
Дата:
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