| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dump and pg_dumpall in real life |
| Date: | 2013-11-12 02:43:43 |
| Message-ID: | CAFcNs+qGXuraex5kvWja6sCiTK_PXOFrcAaNwT=YYxbtgQynFw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Nov 11, 2013 at 8:20 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>
> [...]
>
> Well, then we just need pg_restore to handle the "role already exists"
> error message gracefully. That's all. Or a "CREATE ROLE IF NOT EXISTS"
> statement, and use that for roles.
>
I'm working in a patch to add IF NOT EXISTS for all CREATE statements,
including of course the CREATE ROLE statement.
Regards,
--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-11-12 02:46:09 | Re: MVCC snapshot timing |
| Previous Message | Tom Lane | 2013-11-12 02:27:15 | Re: MVCC snapshot timing |