Hi all,
I have a fresh installation of 8.0devel but I'm not able to
perform any backup using pg_dump:


$ pg_dump -p 5433 test
pg_dump: could not parse ACL list ([0:1]={postgres=UC/postgres,=UC/postgres}) for object "public" (SCHEMA)



Regards
Gaetano Mendola



Thu, 05 Aug 2004 16:02:36 +0200
Gaetano Mendola <mendola@bigfoot.com>
pg_dump: could not parse ACL list
Gaetano Mendola <mendola@bigfoot.com> writes:
> $ pg_dump -p 5433 test
> pg_dump: could not parse ACL list ([0:1]={postgres=UC/postgres,=UC/postgres}) for object "public" (SCHEMA)

Ugh.  This is an unforeseen side effect of Joe's recent changes to make
array_out emit dimension info.

I think the most reasonable answer is to tweak the ACL code so that it
creates ACL arrays with lower bound 1 instead of lower bound 0.  The
only possible downside is that this would confuse any client code that
is manually manipulating ACL arrays and knows about the lower-bound-0
behavior ... but any such code is likely broken anyway by the other ACL
changes that have gone on lately ...

			regards, tom lane

Fri, 06 Aug 2004 13:19:38 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: pg_dump: could not parse ACL list 
Tom Lane wrote:
> Gaetano Mendola <mendola@bigfoot.com> writes:
>>$ pg_dump -p 5433 test
>>pg_dump: could not parse ACL list ([0:1]={postgres=UC/postgres,=UC/postgres}) for object "public" (SCHEMA)
> 
> Ugh.  This is an unforeseen side effect of Joe's recent changes to make
> array_out emit dimension info.

Sorry about that :(. I guess I haven't tried dumping any databases since 
making the change.

> I think the most reasonable answer is to tweak the ACL code so that it
> creates ACL arrays with lower bound 1 instead of lower bound 0.  The
> only possible downside is that this would confuse any client code that
> is manually manipulating ACL arrays and knows about the lower-bound-0
> behavior ... but any such code is likely broken anyway by the other ACL
> changes that have gone on lately ...

At least it looks like it was an easy fix :).

Thanks,

Joe

Fri, 06 Aug 2004 13:48:51 -0700
Joe Conway <mail@joeconway.com>
Re: pg_dump: could not parse ACL list
>>$ pg_dump -p 5433 test
>>pg_dump: could not parse ACL list ([0:1]={postgres=UC/postgres,=UC/postgres}) for object "public" (SCHEMA)
> 
> Ugh.  This is an unforeseen side effect of Joe's recent changes to make
> array_out emit dimension info.
> 
> I think the most reasonable answer is to tweak the ACL code so that it
> creates ACL arrays with lower bound 1 instead of lower bound 0.  The
> only possible downside is that this would confuse any client code that
> is manually manipulating ACL arrays and knows about the lower-bound-0
> behavior ... but any such code is likely broken anyway by the other ACL
> changes that have gone on lately ...

Yes, phpPgAdmin is currently broken either way methinks.

Chris


Sat, 07 Aug 2004 18:02:33 +0800
Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Re: pg_dump: could not parse ACL list