Re: pg_upgrade and materialized views

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_upgrade and materialized views
Date: 2018-02-20 22:13:03
Message-ID: CAGTBQpY+NQQmSxpi=c+T+JZEjYBrVNaiZ=_jExhTwix-o=T+PQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Feb 20, 2018 at 7:08 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Claudio Freire <klaussfreire(at)gmail(dot)com> writes:
>>> Looking into this I also saw:
>>> * set_frozenxids()
>>> which makes a bit uncomfortable, but I can't quite put my finger on
>>> why.
>
>> I looked into that one, it's not relevant to this case, since it's
>> working on template1 (check the conn used there).
>
> Hm? Looks to me like it iterates through all the DBs in the cluster.
>
> regards, tom lane

You're right. But IIUC it's called before restoring globals, so only
postgres, template0 and template1 exist at that point.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2018-02-20 22:17:09 Re: pg_upgrade and materialized views
Previous Message Tom Lane 2018-02-20 22:08:01 Re: pg_upgrade and materialized views