From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Felix Ostmann <felix(dot)ostmann(at)gmail(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: pg_dump ignore CASTs when using --schema |
Date: | 2016-03-04 18:23:25 |
Message-ID: | 29576.1457115805@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Felix Ostmann <felix(dot)ostmann(at)gmail(dot)com> writes:
> we have a problem with pg_dump and CAST.
Casts don't have names, therefore they don't have schemas, therefore
a dump that is restricted to a particular schema won't select them.
So this isn't a bug; it's operating as designed.
This is kind of unfortunate in many scenarios, but it's hard to see a
principled way around it. You might propose something like pretending
that a cast is in the same schema as its implementation function, but
what about casts that have no implementation function? Likewise,
tying it to the schema of either the input or the output datatype
seems arbitrary and about as likely to be wrong as right.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-03-04 18:28:40 | Re: BUG #13844: Logical decoding bug with subxact + row locking |
Previous Message | Andres Freund | 2016-03-04 18:12:10 | Re: BUG #13844: Logical decoding bug with subxact + row locking |