Re: problems with making relfilenodes 56-bits - Mailing list pgsql-hackers
From | Dilip Kumar |
---|---|
Subject | Re: problems with making relfilenodes 56-bits |
Date | |
Msg-id | CAFiTN-sDmhLK3DPXUSDGK21bHt4s4qHZO_My4Gvvh8aGJS6KjQ@mail.gmail.com Whole thread Raw |
In response to | Re: problems with making relfilenodes 56-bits (Andres Freund <andres@anarazel.de>) |
List | pgsql-hackers |
On Sat, Oct 1, 2022 at 5:50 AM Andres Freund <andres@anarazel.de> wrote: > > Hi, > > On 2022-09-30 15:36:11 +0530, Dilip Kumar wrote: > > I have done some testing around this area to see the impact on WAL > > size especially when WAL sizes are smaller, with a very simple test > > with insert/update/delete I can see around an 11% increase in WAL size > > [1] then I did some more test with pgbench with smaller scale > > factor(1) there I do not see a significant increase in the WAL size > > although it increases WAL size around 1-2%. [2]. > > I think it'd be interesting to look at per-record-type stats between two > equivalent workload, to see where practical workloads suffer the most > (possibly with fpw=off, to make things more repeatable). While testing pgbench, I dumped the wal sizes using waldump. So in pgbench case, most of the record sizes increased by 4 bytes as they include single block references and the same is true for the other test case I sent. Here is the wal dump of what the sizes look like for a single pgbench transaction[1]. Maybe for seeing these changes with the different workloads we can run some of the files from the regression test and compare the individual wal sizes. Head: rmgr: Heap len (rec/tot): 54/ 54, tx: 867, lsn: 0/02DD1280, prev 0/02DD1250, desc: LOCK off 44: xid 867: flags 0x01 LOCK_ONLY EXCL_LOCK , blkref #0: rel 1663/5/16424 blk 226 rmgr: Heap len (rec/tot): 171/ 171, tx: 867, lsn: 0/02DD12B8, prev 0/02DD1280, desc: UPDATE off 44 xmax 867 flags 0x11 ; new off 30 xmax 0, blkref #0: rel 1663/5/16424 blk 1639, blkref #1: rel 1663/5/16424 blk 226 rmgr: Btree len (rec/tot): 64/ 64, tx: 867, lsn: 0/02DD1368, prev 0/02DD12B8, desc: INSERT_LEAF off 290, blkref #0: rel 1663/5/16432 blk 39 rmgr: Heap len (rec/tot): 78/ 78, tx: 867, lsn: 0/02DD13A8, prev 0/02DD1368, desc: HOT_UPDATE off 15 xmax 867 flags 0x10 ; new off 19 xmax 0, blkref #0: rel 1663/5/16427 blk 0 rmgr: Heap len (rec/tot): 74/ 74, tx: 867, lsn: 0/02DD13F8, prev 0/02DD13A8, desc: HOT_UPDATE off 9 xmax 867 flags 0x10 ; new off 10 xmax 0, blkref #0: rel 1663/5/16425 blk 0 rmgr: Heap len (rec/tot): 79/ 79, tx: 867, lsn: 0/02DD1448, prev 0/02DD13F8, desc: INSERT off 9 flags 0x08, blkref #0: rel 1663/5/16434 blk 0 rmgr: Transaction len (rec/tot): 46/ 46, tx: 867, lsn: 0/02DD1498, prev 0/02DD1448, desc: COMMIT 2022-10-01 11:24:03.464437 IST Patch: rmgr: Heap len (rec/tot): 58/ 58, tx: 818, lsn: 0/0218BEB0, prev 0/0218BE80, desc: LOCK off 34: xid 818: flags 0x01 LOCK_ONLY EXCL_LOCK , blkref #0: rel 1663/5/100004 blk 522 rmgr: Heap len (rec/tot): 175/ 175, tx: 818, lsn: 0/0218BEF0, prev 0/0218BEB0, desc: UPDATE off 34 xmax 818 flags 0x11 ; new off 8 xmax 0, blkref #0: rel 1663/5/100004 blk 1645, blkref #1: rel 1663/5/100004 blk 522 rmgr: Btree len (rec/tot): 68/ 68, tx: 818, lsn: 0/0218BFA0, prev 0/0218BEF0, desc: INSERT_LEAF off 36, blkref #0: rel 1663/5/100010 blk 89 rmgr: Heap len (rec/tot): 82/ 82, tx: 818, lsn: 0/0218BFE8, prev 0/0218BFA0, desc: HOT_UPDATE off 66 xmax 818 flags 0x10 ; new off 90 xmax 0, blkref #0: rel 1663/5/100007 blk 0 rmgr: Heap len (rec/tot): 78/ 78, tx: 818, lsn: 0/0218C058, prev 0/0218BFE8, desc: HOT_UPDATE off 80 xmax 818 flags 0x10 ; new off 81 xmax 0, blkref #0: rel 1663/5/100005 blk 0 rmgr: Heap len (rec/tot): 83/ 83, tx: 818, lsn: 0/0218C0A8, prev 0/0218C058, desc: INSERT off 80 flags 0x08, blkref #0: rel 1663/5/100011 blk 0 rmgr: Transaction len (rec/tot): 46/ 46, tx: 818, lsn: 0/0218C100, prev 0/0218C0A8, desc: COMMIT 2022-10-01 11:11:03.564063 IST -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
pgsql-hackers by date: