| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE ... SET STORAGE does not propagate to indexes |
| Date: | 2020-03-30 16:23:44 |
| Message-ID: | CAMjNa7eGGceyHROFSwXUtZB8dz2zUFrbU_=CJUqY-Z2QrBB-nw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> ALTER TABLE ... SET STORAGE does not propagate to indexes, even though
> indexes created afterwards get the new storage setting. So depending on
> the order of commands, you can get inconsistent storage settings between
> indexes and tables.
I've absolutely noticed this behavior, I just thought it was intentional
for some reason.
Having this behavior change as stated above would be very welcome in my
opinion. It's always something i've had to manually think about in my
migration scripts, so it would be welcome from my view.
-Adam
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-03-30 16:24:06 | Re: snapper vs. HEAD |
| Previous Message | Mark Dilger | 2020-03-30 16:20:15 | Re: Make autovacuum sort tables in descending order of xid_age |