Re: [GENERAL] tuple data size and compression - Mailing list pgsql-general

From Tom DalPozzo
Subject Re: [GENERAL] tuple data size and compression
Date
Msg-id CAK77FCSVNOS1B_ijgH1JtOe2Y+8AfTL=2a-+qUkZm18x0qyKRQ@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] tuple data size and compression  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general

Two questions:

1) Do you know what your data in the future is going to be?

2) Is a 100 byte bytea a realistic approximation of that data?

wal_compression=off.

--
Adrian Klaver
adrian.klaver@aklaver.com

Hi,
1)  not precisely, but 10/100 million insertions per day. I can't know, it depends on the success of all the system, whose the DB is a part only.
2) It will depend on my implementation which, in turn, depends on these tests... Could be between 100 and 1000 bytes.
If 2) is 1000 random bytes, I saw that, with continuous archiveing (I'm still evaluating if keeping it or not), I get 4KB/row IO write that,
in one year could become 70TB...
Anyway, I will perform my tests with realistic patterns
Regards
Pupillo


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: [GENERAL] Allow login on slave only
Next
From: Guyren Howe
Date:
Subject: [GENERAL] Love Your Database project — Thoughts on effectively handling constraints?