Hello,
It seems that I am running into this issue as well.
Is it likely that this would ever be a config option?
Best,
Pierre Barre
On Fri, May 3, 2024, at 05:11, Riku Iki wrote:
> I did the testing and confirmed that this was the issue.
>
> I run following query:
>
> create table t as selec
I did the testing and confirmed that this was the issue.
I run following query:
create table t as select '1234567890' from generate_series(1, 10);
I commented if (numblocks > 8) codeblock, and see the following results
from "compsize /dbdir/" command.
Before my changes:
Processed 138
Thank you, I have such a system. I think my task would be to compile PG
from sources(need to learn this), and see how it works with and without
that code block.
On Thu, Apr 25, 2024 at 2:25 PM Thomas Munro wrote:
> On Fri, Apr 26, 2024 at 4:37 AM Riku Iki wrote:
> > I am wondering if there were
On Fri, Apr 26, 2024 at 4:37 AM Riku Iki wrote:
> I am wondering if there were preallocation related changes in PG16, and if it
> is possible to disable preallocation in PostgreSQL 16?
I have no opinion on the btrfs details, but I was wondering if someone
might show up with a system that doesn't
eSQL 16?
I posted
<https://dba.stackexchange.com/questions/338906/preallocation-changes-in-postgresql-16>
this on StackExchange, and someone pointed on this commit
<https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=00d1e02be24987180115e371abaeb84738257ae2>
as possible reason of s