| From: | Emre Hasegeli <emre(at)hasegeli(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GiST support for inet datatypes |
| Date: | 2014-02-27 10:39:05 |
| Message-ID: | CAE2gYzzYkthDHc0M61Tm+fGbRAV9dQgk19A=kR7N3F5XbCabXg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2014-02-24 17:55, Bruce Momjian <bruce(at)momjian(dot)us>:
> pg_upgrade has _never_ modified the old cluster, and I am hesitant to do
> that now. Can we make the changes in the new cluster, or in pg_dump
> when in binary upgrade mode?
It can be possible to update the new operator class in the new cluster
as not default, before restore. After the restore, pg_upgrade can upgrade
the btree_gist extension and reset the operator class as the default.
pg_upgrade suggests to re-initdb the new cluster if it fails, anyway. Do
you think it is a better solution? I think it will be more complicated
to do in pg_dump when in binary upgrade mode.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christian Kruse | 2014-02-27 10:44:27 | Re: Patch: show relation and tuple infos of a lock to acquire |
| Previous Message | KONDO Mitsumasa | 2014-02-27 10:38:25 | What behavior is in this loop? |