Re: [BUG] hstore integer overflow when constructing large values

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Keyerror Smart <smartkeyerror(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] hstore integer overflow when constructing large values
Date: 2026-08-18 05:40:18
Message-ID: CAHewXNmF-YKJ+FyuUh0XP6djjWP_Mr_6Jr8bKEkFjEfqHco_PQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Michael Paquier <michael(at)paquier(dot)xyz> 于2026年8月18日周二 13:37写道：
>
> On Mon, Aug 17, 2026 at 01:05:22PM +0900, Michael Paquier wrote:
> > The nested calls in hstore_out() feel a bit inelegant as well written
> > this way. Something in sequential form would feel much easier to
> > parse, with one line for each add_size involved.
>
> Cleaned up a bit all that, and applied on HEAD.

Thanks for pushing.

--
Thanks,
Tender Wang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2026-08-18 05:45:57 Re: Introduce XID age based replication slot invalidation
Previous Message Michael Paquier 2026-08-18 05:37:02 Re: [BUG] hstore integer overflow when constructing large values