On 07/03/2017 05:16 PM, Rafael Martinez wrote:
> We have a discussion about this some time ago and we created a wiki page
> where we tried to write down some ideas/proposals and links to threads
> discussing the subject:
>
> https://wiki.postgresql.org/wiki/Pg_dump_improvements
Thanks for this li
On 06/29/2017 06:30 PM, Adrien Nayrat wrote:
> As reported by Ronan there's no other option than using pg_dumpall to restore
> database options and ACLs.
>
> So, we use this trick to stop pg_dumpall before \connect and then use
> pg_restore:
>
> pg_dumpall -s | sed -rn '/^\\connect/{q}; p' >
On Thu, Jun 29, 2017 at 12:30 PM, Adrien Nayrat
wrote:
> As reported by Ronan there's no other option than using pg_dumpall to restore
> database options and ACLs.
>
> So, we use this trick to stop pg_dumpall before \connect and then use
> pg_restore:
>
> pg_dumpall -s | sed -rn '/^\\connect/{q};
On 12/08/2014 04:21 PM, Ronan Dunklau wrote:
> Hello.
>
> As of now, the only way to restore database options and ACLs is to use
> pg_dumpall without the globals options. The often recommended pg_dumpall -g +
> individual dumps of the target databases doesn't restore those.
>
> Since pg_dump/pg
Hello.
As of now, the only way to restore database options and ACLs is to use
pg_dumpall without the globals options. The often recommended pg_dumpall -g +
individual dumps of the target databases doesn't restore those.
Since pg_dump/pg_restore offer the ability to create the database, it shoul
