From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Sean Flaherty <sflaherty@grndwork.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Increased storage size of jsonb in pg15
Date: Thu, 14 Dec 2023 08:16:09 -0800
Message-ID: <f9aaaaa6-c2e2-4682-861d-81bbc05bc776@aklaver.com> (raw)
In-Reply-To: <CAOscTZNAdqiS4kF1ESW5+6eUMtrzR6WyZXgtd0RUTkbramnk3Q@mail.gmail.com>
References: <CAOscTZMM5QvuXLUN5yE90w=dM+X=6saJR_1ABiOTtt+Y9G3KnQ@mail.gmail.com>
<87680387-ed25-41ff-b6de-37e357398df9@aklaver.com>
<CAOscTZPUcBzWoBqZobvaQ33F1JscsaabjMfi+DSZk07A8HqJPQ@mail.gmail.com>
<ce378740-2da4-4bf4-a750-9556ae059c53@aklaver.com>
<CAOscTZNAdqiS4kF1ESW5+6eUMtrzR6WyZXgtd0RUTkbramnk3Q@mail.gmail.com>
On 12/14/23 06:48, Sean Flaherty wrote:
> We have a process that runs once an hour to read the .dat file in csv
> format then a node script using the pg package
> <https://github.com/brianc/node-postgres; version "8.8.0" to create the
> json objects and insert the data records as jsonb data.
Now I am not understanding.
1) In your OP you mentioned checking size of the column storage using
pg_column_size, yet what you show for increase in size are datafile.dat.
2) So how is datafile.dat related to this issue?
3) Show how you are determining that the storage in the database has
increased in size.
>
> None of the upload process changed during the underlying database upgrade.
>
>
> On Wed, Dec 13, 2023 at 4:56 PM Adrian Klaver <adrian.klaver@aklaver.com
> <mailto:adrian.klaver@aklaver.com>> wrote:
>
> On 12/13/23 15:49, Sean Flaherty wrote:
> > More information needed:
> >
>
> > 2) An example of reported size for the 14.? and 15.5 cases.
> >
> > Since upgrading from 14.8 to 15.5, the jsonb data that was
> previously
> > written in 14.8 is reporting a smaller size than the same hourly
> data
> > written after the upgrade (upgrade indicated in yellow):
>
> What is producing datafile.dat and how?
>
> >
> > *file* *hourly_timestamp* *filename_bytes*
> *timestamp_bytes*
> > *data_filesize* *created_at_bytes* *updated_at_bytes*
> > datafile.dat 2023-10-19 12:00:00 23 8 1682 8
> 8
> > datafile.dat 2023-10-19 13:00:00 23 8 1687 8
> 8
> > datafile.dat 2023-10-19 14:00:00 23 8 1685 8
> 8
> > datafile.dat 2023-10-19 15:00:00 23 8 1668 8
> 8
> > datafile.dat 2023-10-19 16:00:00 23 8 2155 8
> 8
> > datafile.dat 2023-10-19 17:00:00 23 8 2178 8
> 8
> > datafile.dat 2023-10-19 18:00:00 23 8 2199 8
> 8
> > datafile.dat 2023-10-19 19:00:00 23 8 2187 8
> 8
> > datafile.dat 2023-10-19 20:00:00 23 8 2180 8
> 8
> > datafile.dat 2023-10-19 21:00:00 23 8 2176 8
> 8
> > datafile.dat 2023-10-19 22:00:00 23 8 2053 8
> 8
> > datafile.dat 2023-10-19 23:00:00 23 8 2043 8
> 8
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: adrian.klaver@aklaver.com, sflaherty@grndwork.com
Subject: Re: Increased storage size of jsonb in pg15
In-Reply-To: <f9aaaaa6-c2e2-4682-861d-81bbc05bc776@aklaver.com>
References: <CAOscTZMM5QvuXLUN5yE90w=dM+X=6saJR_1ABiOTtt+Y9G3KnQ@mail.gmail.com> <87680387-ed25-41ff-b6de-37e357398df9@aklaver.com> <CAOscTZPUcBzWoBqZobvaQ33F1JscsaabjMfi+DSZk07A8HqJPQ@mail.gmail.com> <ce378740-2da4-4bf4-a750-9556ae059c53@aklaver.com> <CAOscTZNAdqiS4kF1ESW5+6eUMtrzR6WyZXgtd0RUTkbramnk3Q@mail.gmail.com> <f9aaaaa6-c2e2-4682-861d-81bbc05bc776@aklaver.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox