Re: Cache invalidation after authentication (on-the-fly role creation)
Thomas Munro <thomas.munro@enterprisedb.com>
From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-07-04T09:37:41Z
Lists: pgsql-hackers
Attachments
- 0001-Call-AcceptInvalidationMessages-after-authenticat-v2.patch (application/octet-stream) patch v2-0001
On Wed, Jul 4, 2018 at 4:35 PM, Michael Paquier <michael@paquier.xyz> wrote: > I wanted to comment on that this morning but forgot as my mind was > driven away by another problem. What if you used the Julien-Rouhaud's > method of a custom script with only ";" used as query and -c? This > won't run any queries, and will stress authentication. Ok, I tried "pgbench -c 8 -j 8 -T 60 --connect -f empty.sql postgres" where empty.sql contains just ";", and the numbers were noisy but around 1160 TPS with or without a patch. On Wed, Jul 4, 2018 at 4:35 PM, Andres Freund <andres@anarazel.de> wrote: > On 2018-07-04 16:25:18 +1200, Thomas Munro wrote: >> PerformAuthentication(MyProcPort); >> + AcceptInvalidationMessages(); >> InitializeSessionUserId(username, useroid); > > FWIW, a comment explaining why it's done there seems appropriate. Done. -- Thomas Munro http://www.enterprisedb.com
Commits
-
Accept invalidation messages in InitializeSessionUserId().
- e8d9caa436db 12.0 landed