On Thu, Aug 30, 2012 at 9:44 PM, Wahlstedt Jyrki wrote:
>
> On 29.8.2012, at 14.26, Dave Page wrote:
>
> On Tue, Aug 28, 2012 at 9:05 PM, Wahlstedt Jyrki wrote:
>>
>> Dear all,
>> in March I experienced a reproducible crashing problem in pgAdmin3
>> (doubleclick on a table name on right-hand sid
Fix the search query
It tried to look into the pg_user_mapping catalog. A regular user cannot read
this table, hence a query error when searching objects while connected as a
regular user.
This patch adds a new IsSuperuser() method to the pgConn class. It calls this
method to check if it should a
Fix the search query
It tried to look into the pg_user_mapping catalog. A regular user cannot read
this table, hence a query error when searching objects while connected as a
regular user.
This patch adds a new IsSuperuser() method to the pgConn class. It calls this
method to check if it should a
On Mon, 2012-08-27 at 16:57 +0200, Erwin Brandstetter wrote:
> On 27.08.2012 16:37, Erwin Brandstetter wrote:
> > Aloha!
> >
> > I think I ran into this regression with v1.16 beta4 and filed a ticket.
> > So far I have seen this to affect indexes, primary keys and foreign keys
> > But *not* tables,
On Mon, 2012-08-27 at 19:19 +0200, Erwin Brandstetter wrote:
> Aloha!
>
> The SQL script for indexes incorrectly prepends the index name with the table
> name of the involved table - instead of the schema name where the index
> lives.
>
> Demo to reproduce:
> I say:
>
> CREATE TABLE x(nam
On Sun, 2012-08-26 at 18:18 +0200, Guillaume Lelarge wrote:
> On Mon, 2012-07-23 at 08:38 +0100, Dave Page wrote:
> > On Sat, Jul 21, 2012 at 1:40 PM, Guillaume Lelarge
> > wrote:
> > > On Wed, 2012-06-06 at 10:50 +0600, Timon wrote:
> > >> seems that this commit broke reindexing of selected index
