someone - Search results in mailing lists
Mailing lists >> pgsql-committers >> Thread
2025-05-02 00:17:27 | Re: pgsql: doc: Warn that ts_headline() output is not HTML-safe. (Robins Tharakan)
someone can point me to something I'm doing wrong, or else, I'll revert
Mailing lists >> pgsql-committers >> Thread
2025-04-05 00:40:48 | Re: pgsql: Prevent redeclaration of typedef TocEntry. (Álvaro Herrera)
surely where thou typest "foo" someone someday shall type "supercalifragilisticexpialidocious" (5th Commandment for C programmers)
Mailing lists >> pgsql-committers >> Thread
2025-03-27 08:23:24 | pgsql: Fix query jumbling to account for NULL nodes (David Rowley)
someone wrote; SELECT DISTINCT c1 FROM t; and then; SELECT c1 FROM t ORDER BY c1; these
Mailing lists >> pgsql-committers >> Thread
2025-03-22 21:17:07 | pgsql: plpgsql: make WHEN OTHERS distinct from WHEN SQLSTATE '00000'. (Tom Lane)
someone has written code like this and would be annoyed by changing the behavior in a minor
Mailing lists >> pgsql-committers >> Thread
2025-03-20 23:23:15 | pgsql: Be more paranoid in configure's checks for CRC and POPCNT intrin (Tom Lane)
someone. Discussion: https:///m/3368102.1741993462@sss.pgh.pa.us Branch ------ master Details
Mailing lists >> pgsql-committers >> Thread
2025-03-19 05:42:41 | pgsql: Increase io_combine_limit range to 1MB. (Thomas Munro)
Someone would need to research the trade-offs of raising that number. NB if trying
Mailing lists >> pgsql-committers >> Thread
2025-02-20 19:40:05 | pgsql: Ignore blank lines in pgindent exclude files (Andrew Dunstan)
someone would want. If they really want that they can use a wildcard regex to do it. Author
Mailing lists >> pgsql-committers >> Thread
2025-02-11 20:49:46 | pgsql: Detect whether plpgsql assignment targets are "local" variables. (Tom Lane)
someone thinks of a use for that data. I added a bit of plpgsql_dumptree
Mailing lists >> pgsql-committers >> Thread
2024-12-24 16:05:59 | pgsql: Remove pgrminclude and associated scripts (Peter Eisentraut)
someone tried to do something with pgrminclude was around 2011. And it's always had a tendency
Mailing lists >> pgsql-committers >> Thread
2024-12-24 13:59:40 | pgsql: Remove pgrminclude annotations (Peter Eisentraut)
someone tried to do something with pgrminclude was around 2011. Many (not all) of the "pgrminclude
Mailing lists >> pgsql-committers >> Thread
2024-12-11 12:35:50 | pgsql: Enable BUFFERS with EXPLAIN ANALYZE by default (David Rowley)
someone were to come forward with a convincing enough reason as to why doing this
Mailing lists >> pgsql-committers >> Thread
2024-11-04 18:26:37 | pgsql: pg_combinebackup: Error if incremental file exists in full backu (Robert Haas)
someone is intentionally trying to break incremental backup, but per discussion, let's consider that
Mailing lists >> pgsql-committers >> Thread
2024-11-04 18:26:37 | pgsql: pg_combinebackup: Error if incremental file exists in full backu (Robert Haas)
someone is intentionally trying to break incremental backup, but per discussion, let's consider that
Mailing lists >> pgsql-committers >> Thread
2024-10-11 23:38:39 | pgsql: Avoid mixing custom and OpenSSL BIO functions (Daniel Gustafsson)
someone could accidentally call BIO_CTRL_EOF on us so implement mainly for completeness sake
Mailing lists >> pgsql-committers >> Thread
2024-08-14 06:12:38 | pgsql: Remove TRACE_SORT macro (Peter Eisentraut)
someone wanted to disable it. So just remove the macro to simplify things. (For the avoidance