| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | Florents Tselai <florents(dot)tselai(at)gmail(dot)com> |
| Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Force re-compression with lz4 |
| Date: | 2021-10-18 06:46:40 |
| Message-ID: | CA+bJJbxPPSsuRaj1FpcNvv+-xpP8BSc7dqDd1uydcvkE-nvkOQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 17 Oct 2021 at 21:04, Florents Tselai <florents(dot)tselai(at)gmail(dot)com> wrote:
> Yes, That COPY-delete-COPY sequence is what I ended up doing.
> Unfortunately can’t use ranges as the PK its a text string.
Unless you have a really weird PK and have trouble calculating bounds,
text strings are sortable and fine to use as ranges. If you use
half-open intervals you no not even need to query them all (i.e., do a
batch fo key<'aa', then one for >='aa', <'ab', repeat, terminate with
a >='zz' ( substitute letter pairs for whatever you think will
partition your keys in adequate chunks ) ( you can find adequate
bounds scanning the pkindex and skipping, just rememberto sue
half-open intervals and cover all the key domain ).
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florents Tselai | 2021-10-18 06:57:11 | Re: Force re-compression with lz4 |
| Previous Message | Michael Paquier | 2021-10-18 05:18:10 | Re: Force re-compression with lz4 |