| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Robert Treat <rob(at)xzilla(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, Rithvika Devisetti <devisettirithvika(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Teach pg_upgrade to deal with invalid databases |
| Date: | 2026-11-05 15:25:01 |
| Message-ID: | auyfzTok3J3sI0O0@nathan |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Here is what I have staged for commit, which I'm planning to do soon.
Thinking ahead to the automatic deletion project, I wonder if we should
make DROP DATABASE work more like CHECKPOINT. That is, it would mark the
database for deletion, but another process would do the actual work. That
way, dropping a database follows the same path every time, regardless of
whether the DROP command was interrupted. This would also open the door
for a DROP DATABASE option to initiate the drop without waiting for it to
complete, although I'm admittedly not sure that has many use-cases.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Teach-pg_upgrade-to-skip-invalid-databases.patch | text/plain | 8.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | Fujii Masao | 2026-11-05 15:24:00 | Re: file_fdw: Fix ANALYZE does not enforce REJECT_LIMIT with on_error 'ignore' |