From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Robert Treat <rob(at)xzilla(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: small_cleanups around login event triggers |
Date: | 2024-03-14 12:21:29 |
Message-ID: | 722CE5D7-31DE-411A-8ED7-D44D8DDF6CD6@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 14 Mar 2024, at 02:47, Robert Treat <rob(at)xzilla(dot)net> wrote:
> I was taking a look at the login event triggers work (nice work btw)
Thanks for reviewing committed code, that's something which doesn't happen
often enough and is much appreciated.
> and saw a couple of minor items that I thought would be worth cleaning
> up. This is mostly just clarifying the exiting docs and code comments.
+ either in a connection string or configuration file. Alternativly, you can
This should be "Alternatively" I think.
- canceling connection in <application>psql</application> wouldn't cancel
+ canceling a connection in <application>psql</application> will not cancel
Nitpickery (perhaps motivated by english not being my first language), but
since psql only deals with one connection I would expect this to read "the
connection".
- * Returns true iff the lock was acquired.
+ * Returns true if the lock was acquired.
Using "iff" here is being consistent with the rest of the file (and technically
correct):
$ grep -c "if the lock was" src/backend/storage/lmgr/lmgr.c
1
$ grep -c "iff the lock was" src/backend/storage/lmgr/lmgr.c
5
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Jelte Fennema-Nio | 2024-03-14 12:30:19 | Re: Flushing large data immediately in pqcomm |
Previous Message | Robert Haas | 2024-03-14 12:12:36 | Re: Flushing large data immediately in pqcomm |