On Tue, Oct 18, 2016 at 6:28 AM, Tom Lane wrote:
> Heikki Linnakangas writes:
>> Use OpenSSL EVP API for symmetric encryption in pgcrypto.
>
> BTW, "narwhal" seems to have a problem with this.
> Not very clear what, maybe an incompatibility with old openssl versions?
Details are here:
http://bui
Heikki Linnakangas writes:
> Use OpenSSL EVP API for symmetric encryption in pgcrypto.
BTW, "narwhal" seems to have a problem with this.
Not very clear what, maybe an incompatibility with old openssl versions?
regards, tom lane
--
Sent via pgsql-committers mailing list
By default, set log_line_prefix = '%m [%p] '.
This value might not be to everyone's taste; in particular, some
people might prefer %t to %m, and others may want %u, %d, or other
fields. However, it's a vast improvement on the old default of ''.
Christoph Berg
Branch
--
master
Details
-
Use OpenSSL EVP API for symmetric encryption in pgcrypto.
The old "low-level" API is deprecated, and doesn't support hardware
acceleration. And this makes the code simpler, too.
Discussion: <561274f1.1030...@iki.fi>
Branch
--
master
Details
---
http://git.postgresql.org/pg/commitdiff/5f
Fix use-after-free around DISTINCT transition function calls.
Have tuplesort_gettupleslot() copy the contents of its current table slot
as needed. This is based on an approach taken by tuplestore_gettupleslot().
In the future, tuplesort_gettupleslot() may also be taught to avoid copying
the tuple
Fix use-after-free around DISTINCT transition function calls.
Have tuplesort_gettupleslot() copy the contents of its current table slot
as needed. This is based on an approach taken by tuplestore_gettupleslot().
In the future, tuplesort_gettupleslot() may also be taught to avoid copying
the tuple
Replace PostmasterRandom() with a stronger way of generating randomness.
This adds a new routine, pg_strong_random() for generating random bytes,
for use in both frontend and backend. At the moment, it's only used in
the backend, but the upcoming SCRAM authentication patches need strong
random num
