someone - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 23:55:34 | Re: pg_upgrade: warn about roles with md5 passwords (Nathan Bossart)
someone logs in with an MD5 password) down the road. When we do remove MD5 password
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 21:53:27 | Re: Add log_autovacuum_{vacuum|analyze}_min_duration (Sami Imseih)
someone would want to turn off autovacuum logging but keep autoanalyze logging (or vice versa
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 07:03:27 | Custom Glibc collation version strings under LOCPATH (Thomas Munro)
someone might eventually consider writing and proposing a patch to glibc for that. But in the meantime
Mailing lists >> pgsql-hackers >> Thread
2025-06-04 01:51:42 | Re: Correcting freeze conflict horizon calculation (Melanie Plageman)
someone else] can go back and use this information to tackle it in the future
Mailing lists >> pgsql-hackers >> Thread
2025-06-03 17:25:09 | Re: pg_upgrade: warn about roles with md5 passwords (Heikki Linnakangas)
someone might see it. - If we're worried about printing a list of users with
Mailing lists >> pgsql-hackers >> Thread
2025-06-03 14:22:51 | Re: Suggestions for improving \conninfo output in v18 (Robert Treat)
someone gets confused about the behavior, that seems like the place they'd go to look
Mailing lists >> pgsql-hackers >> Thread
2025-06-02 08:24:44 | SQL:2011 Application Time Update & Delete (Paul Jungwirth)
someone would make it.) Tom & Robert thought that firing the INSERT *ROW* triggers made sense
Mailing lists >> pgsql-hackers >> Thread
2025-05-30 23:55:58 | Re: regdatabase (Tom Lane)
other reg* types, at least until someone shows up with a counterexample. regards, tom lane
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-05-30 11:49:50 | Re: Replication slot is not able to sync up (Amit Kapila)
someone would not use the built-in functionality to sync slots and prefer this API. But going
Mailing lists >> pgsql-hackers >> Thread
2025-05-30 02:32:01 | Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them (Bruce Momjian)
someone from getting superuser privileges in case of a dump/restore? (Yeah, that's me, Mr. Sunshine
Mailing lists >> pgsql-hackers >> Thread
2025-05-29 17:45:03 | Re: Warning -Wclobbered in PG_TRY(...) (Maxim Orlov)
someone who wants to make mountains out of molehills. I just want to make things
Mailing lists >> pgsql-hackers >> Thread
2025-05-26 09:00:46 | Re: Automatically sizing the IO worker pool (Thomas Munro)
someone can bring some more science to this problem. I did read up on Erlang
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-05-25 00:39:01 | Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim, replace, split_part (David E. Wheeler)
someone with access to its contents would have to say for sure. And maybe we don't care
Mailing lists >> pgsql-hackers >> Thread
2025-05-24 17:02:52 | Re: [PATCH] Extending FK check skipping on replicas to ADD FK and TRUNCATE (Hannu Krosing)
someone stands up and says they really intended it to work this way :) On Sat, May 24, 2025 at 3:47 PM Hannu
Mailing lists >> pgsql-hackers >> Thread
2025-05-24 00:29:18 | Re: [WIP]Vertical Clustered Index (columnar store extension) - take2 (Tomas Vondra)
someone in the audience pointed out this patch originally started on Postgres 9.5, and that