parameters - Search results in mailing lists
Mailing lists >> pgsql-hackers >> Thread
2025-05-30 14:30:39 | Optimize shared LWLock acquisition for high-core-count systems (Zhou, Zhiguo)
parameter to control optimization usage Key implementation details: - For LW_SHARED with willwait=true: Uses
Mailing lists >> pgsql-hackers >> Thread
2025-05-30 13:07:42 | RE: Replication slot is not able to sync up (Zhijie Hou (Fujitsu))
parameter to control maximum wait time if this approach seems acceptable. I tested that, when
Mailing lists >> pgsql-hackers >> Thread
2025-05-29 22:04:15 | Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them (Matthias van de Meent)
parameters detail this restriction, which is where I looked. Sorry for the noise, and thank
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-05-28 02:02:48 | Re: Clarification on warning when connecting to 'pgbouncer' database via Pgbouncer (Shaik Mohammad Mujeeb)
parameter, which will break plenty of things besides psql --- pg_dump for instance, and just
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (2)
2025-05-26 05:52:25 | Custom GUCs and typos (Srinath Reddy Sadipiralla)
parameter name "pg_stat_statements.count_something", removing it "pg_stat_statements" is now a reserved
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (6)
2025-05-25 22:53:17 | Re: Fixing memory leaks in postgres_fdw (Tom Lane)
parameters */ /* for storing result tuples */ - PGresult *result; /* result for query */ + BEPGresult *result; /* result for query
Mailing lists >> pgsql-hackers >> Thread
2025-05-23 16:18:04 | Re: Relstats after VACUUM FULL and CLUSTER (Erik Nordström)
parameter in the table_relation_copy_for_cluster() function although all other output parameters are documented
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-05-22 18:30:21 | Re: [Util] Warn and Remove Invalid GUCs (Tom Lane)
parameter name "plpgsql.bogus", removing it 2025-05-22 11:16:45.724 EDT [1526138] DETAIL
Mailing lists >> pgsql-hackers >> Thread >> Search in thread (3)
2025-05-20 12:13:27 | Re: Make wal_receiver_timeout configurable per subscription (vignesh C)
contrast, this is handled automatically during CREATE SUBSCRIPTION, where parameter changes are detected. Regards, Vignesh
Mailing lists >> pgsql-hackers >> Thread
2025-05-20 09:27:30 | Re: [PATCH] Allow parallelism for plpgsql return expression after commit 556f7b7 (Dilip Kumar)
parameter from exec_run_select(). In this particular case, the query itself is returning a single
Mailing lists >> pgsql-hackers >> Thread
2025-05-16 18:06:46 | Document default values for pgoutput options + fix missing initialization for "origin" (Fujii Masao)
parameters (like "binary") are explicitly initialized in parse_output_parameters(), the "origin" parameter is not. Its value
Mailing lists >> pgsql-hackers >> Thread
2025-05-14 18:38:03 | PostgreSQL 18 Beta 1 io_max_concurrency (Jafri, Nazneen)
parameter io_max_concurrency shows 64 whereas the documentation says -1, checking if this is the expected
Mailing lists >> pgsql-hackers >> Thread
2025-05-12 21:18:05 | Re: Small fixes needed by high-availability tools (Ants Aasma)
parameter is a small matter of bikeshedding. There is even an interesting paper on how this
Mailing lists >> pgsql-hackers >> Thread
2025-05-10 20:59:27 | Re: Restrict publishing of partitioned table with a foreign table as partition (Álvaro Herrera)
parameter "publish_via_partition_root" to "true" for publication "pub1" DETAIL: Published partitioned table "tmain
Mailing lists >> pgsql-hackers >> Thread
2025-05-09 20:21:17 | Fix incorrect order of params in comment (Daniel Gustafsson)
parameters) +=item $node->log_check($test_name, $offset, %parameters) Check contents of server logs. -- Daniel