| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Luiz Damim <luizvd(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Default value of serial fields changes after restore |
| Date: | 2012-07-19 19:32:30 |
| Message-ID: | 11607.1342726350@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Thu, Jul 19, 2012 at 1:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> This claim is utter nonsense. If you are having a problem it's not due
>> to the way regclass literals print. Please show a complete example of
>> something failing.
> Is it possible the OP has an "alter user set search_path=..." in their
> original db that's not getting backed up here because they're not
> backing up globals? Seems a more reasonable explanation to me.
That might explain why the literals look different than they used to.
But I still say that if he's getting errors on INSERT, they're coming
from some other cause. A regclass literal is just an OID under the hood
--- it cannot result in a lookup error, because the lookup's already
been done.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick | 2012-07-19 20:23:55 | High CPU on read-only streaming replication server |
| Previous Message | Scott Marlowe | 2012-07-19 19:19:18 | Re: Default value of serial fields changes after restore |