| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16577: Segfault on altering a table located in a dropped tablespace |
| Date: | 2020-09-08 21:37:29 |
| Message-ID: | 20200908213729.GA14993@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-Sep-08, Michael Paquier wrote:
> On Tue, Aug 11, 2020 at 04:04:07PM +0900, Michael Paquier wrote:
> > Hmm. Creating a file for partitioned table would be a completely new
> > thing as well. heap_create() has never created a file for partitioned
> > tables since 10 so this could open to a new class of bugs.
>
> This thread has stalled for a couple of weeks now, and I would tend to
> take the path where we'd basically revert 8725958 and ca41030. That's
> too late for v13 to do anything about that. But not for 14. Any
> opinions?
Well, naturally I oppose this idea.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2020-09-08 23:55:53 | Re: BUG #16577: Segfault on altering a table located in a dropped tablespace |
| Previous Message | Alvaro Herrera | 2020-09-08 17:32:22 | Re: [BUG v13] Crash with event trigger in extension |