| From: | Antonin Houska <ah(at)cybertec(dot)at> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: REPACK (ANALYZE) within transaction block segfaults |
| Date: | 2026-09-02 08:47:26 |
| Message-ID: | 15397.1788338846@localhost |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> On 2026-Sep-02, Fujii Masao wrote:
>
> > + * that's just consistent with VACUUM (FULL, ANALYZE), which is a
> > + * synonym for REPACK (ANALYZE).
> >
> > Is VACUUM (FULL, ANALYZE) really a synonym for REPACK (ANALYZE)?
>
> That's the intent, at least. If there are things that work differently,
> I would strive to change them so that they do work the same. However,
> some such changes might be too invasive for pg19, but I would still see
> about changing those in pg20.
>
> Now, maybe there are things about VACUUM FULL ANALYZE that we don't like
> (perhaps, for instance, they exist solely because of even older
> backwards compatibility concerns) that we would prefer not to have in
> REPACK. I don't know if anything of that sort exists, but if so, I
> would propose to seek decisions for each thing individually.
Maybe the question was about the wording - "synonym" might indicate that both
commands execute the same code. Perhaps the comment should rather say that
REPACK (ANALYZE) is (intended to be) a replacement of VACUUM (FULL, ANALYZE).
--
Antonin Houska
Web: https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nazir Bilal Yavuz | 2026-09-02 08:57:01 | Re: Stabilize recovery conflict stats checks in 031_recovery_conflict.pl |
| Previous Message | Ayush Tiwari | 2026-09-02 08:27:20 | Re: Stabilize recovery conflict stats checks in 031_recovery_conflict.pl |