Re: patch: option --if-exists for pg_dump - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: patch: option --if-exists for pg_dump
Date
Msg-id CAFj8pRC_n+aLU4M51wAUjNJGbUz1+gMuyyC7gAJ0N=NAXD6RqA@mail.gmail.com
Whole thread Raw
In response to Re: patch: option --if-exists for pg_dump  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
Responses Re: patch: option --if-exists for pg_dump  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
List pgsql-hackers
Hello

patch with updated comment

regards

Pavel



2014-01-30 Jeevan Chalke <jeevan.chalke@enterprisedb.com>:
Hi Pavel,

Ok. Good.
Sorry I didn't update my sources. Done now. Thanks
 
 

Also, I didn't quite understand these lines of comments:

                        /*
                         * Descriptor string (te-desc) should not be same as object
                         * specifier for DROP STATEMENT. The DROP DEFAULT has not
                         * IF EXISTS clause - has not sense.
                         */

Will you please rephrase ?

I can try it - .

A content of te->desc is usually substring of DROP STATEMENT with one related exception - CONSTRAINT.
Independent to previous sentence - ALTER TABLE ALTER COLUMN DROP DEFAULT doesn't support IF EXISTS - and therefore it should not be injected.

is it ok?

Fine with me.

Thanks

--
Jeevan B Chalke
Principal Software Engineer, Product Development
EnterpriseDB Corporation
The Enterprise PostgreSQL Company


Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Rushabh Lathia
Date:
Subject: Re: pg_upgrade: make the locale comparison more tolerating