Re: Default value of serial fields changes after restore

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:19:18
Message-ID: CAOR=d=3RS3mHoHgB1umZH0j921uWjgbeFNJ4k0-a6QJk4ThXKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 19, 2012 at 1:13 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Luiz Damim <luizvd(at)gmail(dot)com> writes:
>> After restore, default_value changes to
>> nextval('testtable_id_seq'::regclass) and INSERT's start to fail as the
>> sequence can´t be found on it's schema.
>
> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2012-07-19 19:32:30 Re: Default value of serial fields changes after restore
Previous Message Tom Lane 2012-07-19 19:13:08 Re: Default value of serial fields changes after restore