From: Tom Lane <tgl@sss.pgh.pa.us>
To: movead.li@highgo.ca <movead.li@highgo.ca>
Cc: Daniel Verite <daniel@manitou-mail.org>
Cc: pgsql-hackers <pgsql-hackers@lists.postgresql.org>
Cc: ashutosh.bapat <ashutosh.bapat@2ndquadrant.com>
Subject: Re: A bug when use get_bit() function for a long bytea string
Date: Tue, 07 Apr 2020 11:02:43 -0400
Message-ID: <9172.1586271763@sss.pgh.pa.us> (raw)
In-Reply-To: <2020040713393391866468@highgo.ca>
References: <3ae0e84f-1d80-4f98-b36e-235ebcae4ff6@manitou-mail.org>
<2020040709294706977061@highgo.ca>
<2020040713393391866468@highgo.ca>
"movead.li@highgo.ca" <movead.li@highgo.ca> writes:
> After several patch change by hacker's proposal, I think it's ready to
> commit, can we commit it before doing the code freeze for pg-13?
It would be easier to get this done if you had addressed any of the
objections to the patch as given. Integer-overflow handling is still
missing, and you still are assuming that it's okay to change catalog
entries in released branches.
regards, tom lane
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, movead.li@highgo.ca, daniel@manitou-mail.org, pgsql-hackers@lists.postgresql.org, ashutosh.bapat@2ndquadrant.com
Subject: Re: A bug when use get_bit() function for a long bytea string
In-Reply-To: <9172.1586271763@sss.pgh.pa.us>
* 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