Jumping in here, please be gentle. :)
Contents & Purpose
==
This appears to be a patch to add a new table storage option similar to
`toast_tuple_target` but geared toward compression. As a result, it's been
named `compress_tuple_target`, and allows modifying the threshold where
in
> Setting compress_tuple_target to a higher value won't be negative because the
> toast_tuple_target is used for compression anyways when compress_tuple_target
> is higher than toast_tuple_target.
Ack, you're right. Got my wires crossed. I must have gotten confused by my later
tests that enforced
Another ping on this Incremental Sort patch.
Alexander, you'd noted that you would try to get it into subsequent
Commit Fests with improvements you've been considering, but I don't
see it in anything but 2018-11. Have you abandoned this as a
maintainer? If so, it would be nice to know so someone e
the security
aspect of simply hiding trust auths from the log was considered. Since
this is a new capability, I suppose nothing is really different from
say Postgres 14 and below. Still, it never hurts to ask.
Cheers!
--
Shaun Thomas
High Availability Architect
EDB
www.enterprisedb.com
> We could do something like a LOG "connection: method=%s user=%s
> (%s:%d)", without the "authenticated" and "identity" terms from
> set_authn_id(). Just to drop an idea.
That would be my inclination as well. Heck, just slap a log message
right in the specific case statements that don't have act
