| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, nickbarnes01(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15310: pg_upgrade dissociates event triggers from extensions |
| Date: | 2018-08-07 20:38:03 |
| Message-ID: | 5239.1533674283@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> That sounds like a bug to me. Could you add more tests to
> src/test/modules/test_pg_dump with an event trigger part of an extension
> with a binary upgrade test?
It doesn't seem especially useful to me to lock this particular barn
door behind the horse. What would be great is a way of cross-checking
that the grammar, pg_dump, and the various callers of
recordDependencyOnCurrentExtension are all on the same page about
which objects can be extension members. I see no way to automate that
unfortunately :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Akos Vandra | 2018-08-07 20:50:53 | Re: BUG #15271: Documentation / Error reporting on GUC parameter change |
| Previous Message | Bruce Momjian | 2018-08-07 19:36:47 | Re: BUG #15271: Documentation / Error reporting on GUC parameter change |