Re: The "char" type versus non-ASCII characters

On Fri, Dec 03, 2021 at 03:13:24PM -0500, Tom Lane wrote: > Andrew Dunstan writes: > > On 12/3/21 14:42, Tom Lane wrote: > >> Right, I envisioned that ASCII behaves the same but we'd use > >> a numeric representation for high-bit-set values. These > >> cases could be told apart fairly easily by c

Re: disfavoring unparameterized nested loops

> > > > Most of the time when I see that happen it's down to either the > > selectivity of some correlated base-quals being multiplied down to a > > number low enough that we clamp the estimate to be 1 row. The other > > case is similar, but with join quals. > > If an estimate is lower than 1, t

Re: Add SQL function for SHA1

On Tue, Jan 26, 2021 at 01:06:29PM +0900, Michael Paquier wrote: > On Mon, Jan 25, 2021 at 10:42:25PM -0500, Sehrope Sarkuni wrote: > > +1 to adding a SHA1 SQL function. Even if it's deprecated, there's plenty > > of historical usage that I can see it being useful. > > Let's wait for more opinions

Re: libpq compression

On Tue, Dec 22, 2020 at 07:15:23PM +0100, Tomas Vondra wrote: > > > On 12/22/20 6:56 PM, Robert Haas wrote: > >On Tue, Dec 22, 2020 at 6:24 AM Daniil Zakhlystov > > wrote: > >>When using bidirectional compression, Postgres resource usage correlates > >>with the selected compression level. For ex

Re: Bump default wal_level to logical

On Mon, Jun 08, 2020 at 02:58:03PM -0400, Robert Haas wrote: > On Mon, Jun 8, 2020 at 1:16 PM Alvaro Herrera > wrote: > > I think it's reasonable to push our default limits for slots, > > walsenders, max_bgworkers etc a lot higher than current value (say 10 -> > > 100). An unused slot wastes ess

Re: factorial function/phase out postfix operators?

> > I won't lose a lot of sleep if we decide to rip out '!' as well, but I > don't think that continuing to support it would cost us much. > +1 for keeping ! and nuking the rest, if possible. Regards, Ken

Re: Protect syscache from bloating with negative cache entries

On Tue, Jan 15, 2019 at 01:32:36PM -0500, Tom Lane wrote: > ... > > FYI, Oracle provides one parameter, shared_pool_size, that determine the > > size of a memory area that contains SQL plans and various dictionary > > objects. Oracle decides how to divide the area among constituents. So > > it c

Re: Migration to PGLister - After

Hi, I also find it very useful to be able to identify the list by the subject. The way to address this is, as Geoff mentions, to NOT include subject in your DKIM signature. Regards, Ken On Mon, Nov 13, 2017 at 04:41:59PM +, Geoff Winkless wrote: > The removal of the [HACKERS] (etc) header wi