| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_dumpall --exclude-database option |
| Date: | 2018-12-25 00:55:29 |
| Message-ID: | 20181225005529.GC2334@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 24, 2018 at 02:46:48PM -0500, Andrew Dunstan wrote:
> I think you're mistaken. The following example shows this clearly -
> there is nothing corresponding to the 20 excluded databases. What you're
> referring to appears to be the statements that preceded the 'CREATE
> DATABASE' statement. That's to be excpected.
I would have believed that excluding a database removes a full section
from "PostgreSQL database dump" to "PostgreSQL database dump
complete", and not only a portion of it. Sorry for sounding
nit-picky.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2018-12-25 01:17:13 | Re: GIN predicate locking slows down valgrind isolationtests tremendously |
| Previous Message | Tomas Vondra | 2018-12-25 00:46:51 | Re: Performance issue in foreign-key-aware join estimation |