Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value
От | Nathan Bossart |
---|---|
Тема | Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value |
Дата | |
Msg-id | 20240309145028.GB1111406@nathanxps13 обсуждение исходный текст |
Ответ на | Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value (Yugo NAGATA <nagata@sraoss.co.jp>) |
Ответы |
Re: pg_column_toast_chunk_id: a function to get a chunk ID of a TOASTed value
|
Список | pgsql-hackers |
On Sat, Mar 09, 2024 at 11:57:18AM +0900, Yugo NAGATA wrote: > On Fri, 8 Mar 2024 16:17:58 -0600 > Nathan Bossart <nathandbossart@gmail.com> wrote: >> Is this guaranteed to be TOASTed for all possible page sizes? > > Should we use block_size? > > SHOW block_size \gset > INSERT INTO test_chunk_id(v1,v2) > VALUES (repeat('x', 1), repeat('x', (:block_size / 4))); > > I think this will work in various page sizes. WFM > +SHOW block_size; \gset > + block_size > +------------ > + 8192 > +(1 row) I think we need to remove the ';' so that the output of the query is not saved in the ".out" file. With that change, this test passes when Postgres is built with --with-blocksize=32. However, many other unrelated tests begin failing, so I guess this fix isn't tremendously important. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
В списке pgsql-hackers по дате отправления: