Brendan Jurd wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 18, 2008 at 2:37 AM, Tom Lane wrote:
The function names in the patch need schema-qualification in case
pg_catalog is not first in the search path.
Ah, yes. I should have seen that. Thanks Tom.
New v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, May 4, 2008 at 10:55 AM, Tom Lane wrote:
> Andrew Dunstan writes:
> > Wouldn't this expression:
> > pg_catalog.array_to_string(c.relacl, chr(10))
> > be better expressed as
> > pg_catalog.array_to_string(c.relacl, E'\n')
>
>
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Wouldn't this expression:
> pg_catalog.array_to_string(c.relacl, chr(10))
> be better expressed as
> pg_catalog.array_to_string(c.relacl, E'\n')
+1 ... it's minor, but knowing that ASCII LF is 10 is probably not
wired into too many people's
Brendan Jurd wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 18, 2008 at 2:37 AM, Tom Lane wrote:
The function names in the patch need schema-qualification in case
pg_catalog is not first in the search path.
Ah, yes. I should have seen that. Thanks Tom.
New v
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Apr 18, 2008 at 2:37 AM, Tom Lane wrote:
> The function names in the patch need schema-qualification in case
> pg_catalog is not first in the search path.
>
Ah, yes. I should have seen that. Thanks Tom.
New version attached with schema-q
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> It occurred to me that psql's \z command could benefit from the
> addition of some newlines. With any more than one grantee per object,
> the output of \z rapidly becomes extremely wide, and very hard to
> read.
Seems like a good idea now that psql dea
