On Thu, Jun 15, 2017 at 9:50 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Can you give a concrete example where this would have > helped above and beyond knowing, eg, the source and time of the connection > attempt?
I can imagine that in really high-volume use cases (such as the OP apparently has) the number of client connections might be so large that identification by timestamp isn't useful, and the source IP will be obscured after the first hop through a connection pooler or other middleware. If you've got 100 connections per second coming in, matching things up by timestamp across different machines is going to be tough. But I agree with your other concerns. I think the problem is real, but I'm not sure that this is the best solution. On the other hand, I'm also not entirely sure I understand the proposal yet. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
