Re: pg_dump/restore syntax checking bug?

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump/restore syntax checking bug?
Date: 2013-03-23 13:57:17
Message-ID: 514DB4BD.6060905@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03/22/2013 10:13 PM, Josh Kupershmidt wrote:
>
> On Fri, Mar 22, 2013 at 9:35 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>
>> postgres(at)jd-laptop:~$ pg_restore -d test -P 'by(),hello()' foo.sqlc
>
> Note, the pg_restore doc makes no mention of trying to squeeze
> multiple function prototypes in a single argument you've done here, or
> of using multiple -P flags.
>
>> It appears we need better syntax checking.
>
> Can't really argue with this. But if you think these pg_restore
> examples are bad, try this gem:
> reindexdb --table='foo; ALTER ROLE limited WITH superuser'

That is HORRIBLE! Looks like our base utilities need some attention.

jD

>
> Josh
>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Adrian Klaver 2013-03-23 14:01:41 Re: timeofday() and clock_timestamp() produce different results when casting to timestamptz
Previous Message Andres Freund 2013-03-23 13:55:39 Re: Enabling Checksums