| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: pg_dump: could not parse ACL list |
| Date: | 2004-08-07 10:02:33 |
| Message-ID: | 4114A8B9.2010601@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>$ 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2004-08-07 10:09:13 | Re: [PATCHES] UNICODE characters above 0x10000 |
| Previous Message | John Hansen | 2004-08-07 07:59:39 | Re: UNICODE characters above 0x10000 |