From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | a(dot)kozhemyakin(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17741: vacuum process hangs after pg_surgery manipulations |
Date: | 2023-01-16 15:31:04 |
Message-ID: | 20230116153104.u3xamywpxovvzfo4@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2023-Jan-09, PG Bug reporting form wrote:
> On the REL_15_STABLE, you can hang vacuum freeze. Maybe this is not
> desired?
> https://www.postgresql.org/docs/current/pgsurgery.html
>
> reproduce script:
> create extension pg_surgery;
Using pg_surgery is the equivalent of introducing corruption in your
data. It has, of course, completely valid uses, but if you break the
system while using it, it's on you to fix it.
The pg_surgery documentation you cite states:
: These functions are unsafe by design and using them may corrupt (or
: further corrupt) your database.
So, you've been warned.
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
"It takes less than 2 seconds to get to 78% complete; that's a good sign.
A few seconds later it's at 90%, but it seems to have stuck there. Did
somebody make percentages logarithmic while I wasn't looking?"
http://smylers.hates-software.com/2005/09/08/1995c749.html
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Astapov | 2023-01-16 19:44:36 | Re: BUG #17698: On SIGTERM, psql terminates, but leaves the statement running |
Previous Message | Alvaro Herrera | 2023-01-16 15:14:59 | Re: BUG #17698: On SIGTERM, psql terminates, but leaves the statement running |