# waiting Published articles for waiting. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound DevFeed: [fsGroupChangePolicy: OnRootMismatch and the setgid Invariant That Makes It Sound]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-11T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [container](), [mount](), [Security](), [Process]() Tags: [container](), [container-image](), [kubernetes](), [mount](), [network](), [performance](), [reliability](), [security](), [stateful](), [storage](), [waiting]() ### AI overview This article explains why a stateful pod can remain in ContainerCreating for fifteen minutes when fsGroup triggers a recursive chown across a large network-backed volume. It describes how fsGroupChangePolicy: OnRootMismatch can skip the recursive walk when the volume root group already matches, and discusses the setgid invariant that supports this behavior. ### Source excerpt Pod stuck in ContainerCreating from fsGroup recursive chown: fsGroupChangePolicy: OnRootMismatch, and why the setgid bit on the volume root makes it safe. ## Waiting for PostgreSQL 19 - SQL Property Graph Queries (SQL/PGQ) DevFeed: [Waiting for PostgreSQL 19 - SQL Property Graph Queries (SQL/PGQ)]() Original publisher: [Read original article]() Author: depesz Published: 2026-07-31T16:57:44Z Content type: opinion Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [SQL](), [Graphs](), [function](), [pattern matching]() Tags: [function](), [graph](), [graphs](), [pattern-matching](), [pg19](), [pgq](), [postgresql](), [property](), [sql](), [uncategorized](), [waiting]() ### AI overview The article discusses PostgreSQL's SQL/PGQ implementation for property graph queries, including GRAPH_TABLE, graph pattern matching, and related DDL commands. It notes that the change was later rolled back and expresses the author's uncertainty about the practical benefits and usability of the syntax. ### Source excerpt Important update This change has been rolled back. Discussion can be found here. On 16th of March 2026, Peter Eisentraut committed patch: SQL Property Graph Queries (SQL/PGQ) Implementation of SQL property graph queries, according to SQL/PGQ standard (ISO/IEC 9075-16:2023). This adds: - GRAPH_TABLE table function for graph pattern matching - DDL commands ... Continue reading "Waiting for PostgreSQL 19 - SQL Property Graph Queries (SQL/PGQ)" ## Waiting for PostgreSQL 20 - Add min() and max() aggregate support for uuid. DevFeed: [Waiting for PostgreSQL 20 - Add min() and max() aggregate support for uuid.]() Original publisher: [Read original article]() Author: depesz Published: 2026-07-09T12:41:14Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [DateTime]() Tags: [aggregate](), [btree](), [max](), [min](), [order](), [pg20](), [postgresql](), [sort](), [uncategorized](), [uuid](), [uuid-extract-timestamp](), [waiting]() ### AI overview This article discusses a PostgreSQL patch adding min() and max() aggregate support for the uuid type. It explains that uuid is totally ordered through comparison operators and a btree operator class, and demonstrates the aggregates with UUID v7 and random UUIDs. ### Source excerpt On 1st of July 2026, Masahiko Sawada committed patch: Add min() and max() aggregate support for uuid. The uuid type already has a full set of comparison operators and a btree operator class, so it is totally ordered. min() and max() were the only common aggregates missing for it. Add the uuid_larger() and uuid_smaller() ... Continue reading "Waiting for PostgreSQL 20 - Add min() and max() aggregate support for uuid." ## Waiting for PostgreSQL 20 - Add backend-level lock statistics DevFeed: [Waiting for PostgreSQL 20 - Add backend-level lock statistics]() Original publisher: [Read original article]() Author: depesz Published: 2026-07-06T17:30:55Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [Back end](), [Statistics]() Tags: [backend](), [pg-stat-get-backend-lock](), [pg-stat-lock](), [pg20](), [postgresql](), [statistics](), [uncategorized](), [waiting]() ### AI overview A walkthrough of a PostgreSQL patch that adds per-backend lock statistics, including lock wait counts, wait times, and fast-path exceeded counts. The author demonstrates the feature with concurrent psql sessions and discusses its usefulness for diagnosing lock behavior. ### Source excerpt On 30th of June 2026, Michael Paquier committed patch: Add backend-level lock statistics This commit adds per-backend lock statistics, providing the same information as pg_stat_lock. It is now possible to retrieve those stats (lock wait counts, wait times, and fast-path exceeded count) on a per-backend basis. This data can be retrieved with a ... Continue reading "Waiting for PostgreSQL 20 - Add backend-level lock statistics" ## Timers, Timeouts, and the Art of Waiting in Temporal DevFeed: [Timers, Timeouts, and the Art of Waiting in Temporal]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2026-06-30T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [SDKs](), [Code](), [Processes]() Tags: [concurrent](), [crashes](), [deployment](), [developers](), [how-to](), [scaling](), [sdks](), [temporal-concepts](), [timeout](), [waiting]() ### AI overview This tutorial explains that Temporal timers provide durable business-logic waiting, while Activity and Workflow timeouts detect failures. It describes how timers survive Worker or process failures and can support large numbers of concurrent waits. ### Source excerpt Timers and timeouts look similar in Temporal but solve different problems. Learn how each one works and how to choose the right tool for durable waiting. ## Waiting for PostgreSQL 19 - Add CONCURRENTLY option to REPACK DevFeed: [Waiting for PostgreSQL 19 - Add CONCURRENTLY option to REPACK]() Original publisher: [Read original article]() Author: depesz Published: 2026-04-21T10:40:14Z Content type: opinion Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL]() Tags: [bloat](), [concurrently](), [maintenance](), [pg19](), [postgresql](), [repack](), [uncategorized](), [vacuum](), [waiting]() ### AI overview The article tests PostgreSQL 19's proposed CONCURRENTLY option for REPACK on a table with 200 million rows. The test found that the table shrank as expected, while inserts experienced a visible but limited slowdown during repacking. ### Source excerpt On 6th of April 2026, Álvaro Herrera committed patch: Add CONCURRENTLY option to REPACK When this flag is specified, REPACK no longer acquires access-exclusive lock while the new copy of the table is being created; instead, it creates the initial copy under share-update-exclusive lock only (same as vacuum, etc), and it follows an MVCC ... Continue reading "Waiting for PostgreSQL 19 - Add CONCURRENTLY option to REPACK" ## Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums DevFeed: [Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums]() Original publisher: [Read original article]() Author: depesz Published: 2026-04-15T18:05:36Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql clusters](), [async](), [IO]() Tags: [async](), [background](), [background-work](), [checksums](), [data-checksum](), [io](), [pg19](), [postgresql](), [uncategorized](), [vacuum](), [waiting]() ### AI overview This article examines a PostgreSQL 19 patch that allows data checksums to be enabled or disabled while a cluster is running. The command is immediate, but rewriting every table and index occurs in the background and can require substantial I/O. The article also discusses cost-delay options for controlling the background worker. ### Source excerpt On 3rd of April 2026, Daniel Gustafsson committed patch: Online enabling and disabling of data checksums This allows data checksums to be enabled, or disabled, in a running cluster without restricting access to the cluster during processing. Data checksums could prior to this only be enabled during initdb or when the cluster is ... Continue reading "Waiting for PostgreSQL 19 - Online enabling and disabling of data checksums" ## Waiting for PostgreSQL 19 - new pg\_get\_\*\_ddl() functions DevFeed: [Waiting for PostgreSQL 19 - new pg\_get\_\*\_ddl() functions]() Original publisher: [Read original article]() Author: depesz Published: 2026-04-09T16:37:45Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [SQL](), [Databases]() Tags: [functions](), [pg-dump](), [pg-get-database-ddl](), [pg-get-role-ddl](), [pg-get-tablespace-ddl](), [pg19](), [postgresql](), [schema](), [sql](), [uncategorized](), [waiting]() ### AI overview This article examines proposed PostgreSQL 19 SQL-callable pg_get_*_ddl() functions that generate DDL for recreating databases, roles, and tablespaces. It demonstrates their output and options, notes that role passwords are not exported, and observes that support for additional object types is still missing. ### Source excerpt On 5th of April 2026, Andrew Dunstan committed patch: Add pg_get_database_ddl() function Add a new SQL-callable function that returns the DDL statements needed to recreate a database. It takes a regdatabase argument and an optional VARIADIC text argument for options that are specified as alternating name/value pairs. The following options are supported: pretty (boolean) ... Continue reading "Waiting for PostgreSQL 19 - new pg_get_*_ddl() functions" ## PostgreSQL temporal UPDATE and DELETE by range DevFeed: [PostgreSQL temporal UPDATE and DELETE by range]() Original publisher: [Read original article]() Author: depesz Published: 2026-04-02T10:51:21Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql 18]() Tags: [delete](), [period](), [pg19](), [postgresql](), [query](), [range](), [temporal](), [uncategorized](), [update](), [version](), [waiting]() ### AI overview This article explains a PostgreSQL patch that extends UPDATE and DELETE for temporal tables, allowing changes or deletions over a specified range or multirange period. The article also notes that the patch was later reverted after discussion. ### Source excerpt Important update This has been reverted with some discussion. Thanks for ping to mkurz 🙂 On 1st of April 2026, Peter Eisentraut committed patch: Add UPDATE/DELETE FOR PORTION OF This is an extension of the UPDATE and DELETE commands to do a "temporal update/delete" based on a range or multirange column. The user can ... Continue reading "Waiting for PostgreSQL 19 - Add UPDATE/DELETE FOR PORTION OF" ## Waiting for PostgreSQL 19 - json format for COPY TO DevFeed: [Waiting for PostgreSQL 19 - json format for COPY TO]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-29T12:34:22Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [JSON](), [export](), [data](), [Query (disambiguation)](), [interoperability]() Tags: [command](), [copy](), [data](), [developers](), [export](), [json](), [pg19](), [postgresql](), [query](), [stream](), [uncategorized](), [waiting]() ### AI overview The article discusses a PostgreSQL 19 patch adding a JSON format option to COPY TO. It allows table data or query results to be exported as a stream of JSON objects, one object per line, with an option to wrap the output in an array. ### Source excerpt On 20th of March 2026, Andrew Dunstan committed patch: json format for COPY TO This introduces the JSON format option for the COPY TO command, allowing users to export query results or table data directly as a stream of JSON objects (one per line, NDJSON style). The JSON format is currently supported only ... Continue reading "Waiting for PostgreSQL 19 - json format for COPY TO" ## Waiting for PostgreSQL 19 - Add support for EXCEPT TABLE in ALTER PUBLICATION. DevFeed: [Waiting for PostgreSQL 19 - Add support for EXCEPT TABLE in ALTER PUBLICATION.]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-26T11:46:24Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [syntax]() Tags: [alter](), [commit](), [except](), [logical](), [pg19](), [postgresql](), [publication](), [replication](), [table](), [uncategorized](), [waiting]() ### AI overview This article discusses a PostgreSQL 19 patch adding EXCEPT TABLE support to ALTER PUBLICATION. The change allows modifying a publication's table exclusion list, though the example notes that specifying an exclusion for one publication replaced its previous exclusion list. ### Source excerpt On 20th of March 2026, Amit Kapila committed patch: Add support for EXCEPT TABLE in ALTER PUBLICATION. Following commit fd366065e0, which added EXCEPT TABLE support to CREATE PUBLICATION, this commit extends ALTER PUBLICATION to allow modifying the exclusion list. New Syntax: ALTER PUBLICATION name SET publication_all_object [, ... ] where publication_all_object is ... Continue reading "Waiting for PostgreSQL 19 - Add support for EXCEPT TABLE in ALTER PUBLICATION." ## Waiting for PostgreSQL 19 - Add pg\_plan\_advice contrib module. DevFeed: [Waiting for PostgreSQL 19 - Add pg\_plan\_advice contrib module.]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-22T13:44:10Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [systems]() Tags: [advice](), [hint](), [module](), [pg-plan-advice](), [pg19](), [plan](), [planner](), [postgresql](), [statistics](), [uncategorized](), [waiting]() ### AI overview This article examines PostgreSQL's proposed pg_plan_advice contrib module, explaining why query planners sometimes choose suboptimal plans, how plan hints could stabilize or override those choices, and how to load and test the extension. ### Source excerpt On 12nd of March 2026, Robert Haas committed patch: Add pg_plan_advice contrib module. Provide a facility that (1) can be used to stabilize certain plan choices so that the planner cannot reverse course without authorization and (2) can be used by knowledgeable users to insist on plan choices contrary to what the planner believes ... Continue reading "Waiting for PostgreSQL 19 - Add pg_plan_advice contrib module." ## Waiting for PostgreSQL 19 - Introduce the REPACK command DevFeed: [Waiting for PostgreSQL 19 - Introduce the REPACK command]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-19T18:07:59Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [postgresql clusters]() Tags: [analyze](), [bloat](), [command](), [indexes](), [locking](), [maintenance](), [pg-repack](), [pg19](), [planner](), [postgresql](), [repack](), [uncategorized](), [vacuum](), [waiting]() ### AI overview The article examines PostgreSQL 19's proposed built-in REPACK command, which combines functionality associated with VACUUM FULL and CLUSTER. It demonstrates reclaiming space and reordering a table, discusses locking because concurrent operation is not yet supported, and introduces the pg_stat_progress_repack progress view and available command forms. ### Source excerpt On 10th of March 2026, Álvaro Herrera committed patch: Introduce the REPACK command REPACK absorbs the functionality of VACUUM FULL and CLUSTER in a single command. Because this functionality is completely different from regular VACUUM, having it separate from VACUUM makes it easier for users to understand; as for CLUSTER, the term is heavily ... Continue reading "Waiting for PostgreSQL 19 - Introduce the REPACK command" ## Waiting for PostgreSQL 19 - Allow table exclusions in publications via EXCEPT TABLE. DevFeed: [Waiting for PostgreSQL 19 - Allow table exclusions in publications via EXCEPT TABLE.]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-18T11:15:16Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [Replication](), [Databases]() Tags: [except](), [logical](), [new-feature](), [pg19](), [postgresql](), [publication](), [replication](), [uncategorized](), [waiting]() ### AI overview A PostgreSQL patch adds EXCEPT TABLE support to CREATE PUBLICATION ... FOR ALL TABLES, allowing selected tables to be excluded from logical replication. The article explains the existing publication options and notes that altering an existing FOR ALL TABLES publication to add exclusions is not currently supported. ### Source excerpt On 4th of March 2026, Amit Kapila committed patch: Allow table exclusions in publications via EXCEPT TABLE. Extend CREATE PUBLICATION ... FOR ALL TABLES to support the EXCEPT TABLE syntax. This allows one or more tables to be excluded. The publisher will not send the data of excluded tables to the subscriber. To ... Continue reading "Waiting for PostgreSQL 19 - Allow table exclusions in publications via EXCEPT TABLE." ## Waiting for PostgreSQL 19 - Add non-text output formats to pg\_dumpall DevFeed: [Waiting for PostgreSQL 19 - Add non-text output formats to pg\_dumpall]() Original publisher: [Read original article]() Author: depesz Published: 2026-03-17T10:29:38Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [backups](), [Databases]() Tags: [backup](), [backups](), [compression](), [maintenance](), [pg-dump](), [pg-dumpall](), [pg19](), [postgresql](), [uncategorized](), [waiting]() ### AI overview The article examines a PostgreSQL 19 patch that adds custom, directory, and tar output formats to pg_dumpall. It describes the resulting files and explains how the formats can support more selective restoration and simpler backups. ### Source excerpt On 26th of February 2026, Andrew Dunstan committed patch: Add non-text output formats to pg_dumpall pg_dumpall can now produce output in custom, directory, or tar formats in addition to plain text SQL scripts. When using non-text formats, pg_dumpall creates a directory containing: - toc.glo: global data (roles and tablespaces) in custom format - map.dat: ... Continue reading "Waiting for PostgreSQL 19 - Add non-text output formats to pg_dumpall" ## Waiting for PostgreSQL 19 - Allow log\_min\_messages to be set per process type DevFeed: [Waiting for PostgreSQL 19 - Allow log\_min\_messages to be set per process type]() Original publisher: [Read original article]() Author: depesz Published: 2026-02-21T19:05:27Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [Processes](), [Process]() Tags: [configuration](), [debug](), [log-min-messages](), [logs](), [pg19](), [postgresql](), [process](), [processes](), [uncategorized](), [waiting]() ### AI overview A PostgreSQL 19 change allows log_min_messages to be configured separately for different process types. The article explains the change and lists examples of supported backend and background process types. ### Source excerpt On 9th of February 2026, Álvaro Herrera committed patch: Allow log_min_messages to be set per process type Change log_min_messages from being a single element to a comma-separated list of type:level elements, with 'type' representing a process type, and 'level' being a log level to use for that type of process. The list must also ... Continue reading "Waiting for PostgreSQL 19 - Allow log_min_messages to be set per process type" ## Waiting for PostgreSQL 19 - psql: Add %i prompt escape to indicate hot standby status. DevFeed: [Waiting for PostgreSQL 19 - psql: Add %i prompt escape to indicate hot standby status.]() Original publisher: [Read original article]() Author: depesz Published: 2026-02-21T14:51:47Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [Replication]() Tags: [2026](), [commit](), [pg19](), [postgresql](), [primary](), [psql](), [replication](), [standby](), [uncategorized](), [waiting]() ### AI overview The article explains a PostgreSQL 19 patch that adds the %i prompt escape to psql. The escape indicates whether the connected server is a primary or operating in hot standby mode, making replication status visible in the psql prompt. ### Source excerpt On 3rd of February 2026, Fujii Masao committed patch: psql: Add %i prompt escape to indicate hot standby status. This commit introduces a new prompt escape %i for psql, which shows whether the connected server is operating in hot standby mode. It expands to standby if the server reports in_hot_standby = on, and primary ... Continue reading "Waiting for PostgreSQL 19 - psql: Add %i prompt escape to indicate hot standby status." ## Waiting for PostgreSQL 19 - Implement ALTER TABLE ... MERGE/SPLIT PARTITIONS ... command DevFeed: [Waiting for PostgreSQL 19 - Implement ALTER TABLE ... MERGE/SPLIT PARTITIONS ... command]() Original publisher: [Read original article]() Author: depesz Published: 2026-01-04T17:30:47Z Content type: opinion Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [function]() Tags: [command](), [locking](), [merge](), [partition](), [partitioning](), [partitions](), [pg19](), [postgresql](), [split](), [uncategorized](), [waiting]() ### AI overview A PostgreSQL 19 development update describes the ALTER TABLE command for merging and splitting partitions. The patch was rolled back after earlier discussion, then recommitted; testing showed it worked as expected, with slightly less locking observed. Further changes may be needed before the feature reaches the final release. ### Source excerpt Important update This has been rolled back after some discussion. On 14th of December 2025, Alexander Korotkov committed patch: Implement ALTER TABLE ... MERGE PARTITIONS ... command This new DDL command merges several partitions into a single partition of the target table. The target partition is created using the new createPartitionTable() function with the ... Continue reading "Waiting for PostgreSQL 19 - Implement ALTER TABLE ... MERGE/SPLIT PARTITIONS ... command" ## Waiting for PostgreSQL 19 - Sequence synchronization in logical replication. DevFeed: [Waiting for PostgreSQL 19 - Sequence synchronization in logical replication.]() Original publisher: [Read original article]() Author: depesz Published: 2025-11-11T12:24:23Z Content type: tutorial Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [Replication](), [Sequences]() Tags: [benchmark](), [logical](), [pg19](), [postgresql](), [psql](), [publications](), [replication](), [sequence](), [sequences](), [synchronization](), [uncategorized](), [upgrade](), [upgrades](), [waiting]() ### AI overview This article demonstrates PostgreSQL 19's planned sequence synchronization for logical replication. It sets up source and destination databases, tests sequence synchronization, finds that resynchronization must be manually invoked, and reports that synchronizing 10,000 sequences took about one second in the author's test. ### Source excerpt First, on 9th of October 2025, Amit Kapila committed patch: Add "ALL SEQUENCES" support to publications. This patch adds support for the ALL SEQUENCES clause in publications, enabling synchronization/replication of all sequences that is useful for upgrades. Publications can now include all sequences via FOR ALL SEQUENCES. psql enhancements: \d shows publications for ... Continue reading "Waiting for PostgreSQL 19 - Sequence synchronization in logical replication." ## Waiting for PostgreSQL 19 - Add psql PROMPT variable for search\_path. DevFeed: [Waiting for PostgreSQL 19 - Add psql PROMPT variable for search\_path.]() Original publisher: [Read original article]() Author: depesz Published: 2025-10-29T11:59:17Z Content type: release Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL]() Tags: [commit](), [pg19](), [postgresql](), [prompt](), [prompt1](), [psql](), [query](), [schema](), [schemas](), [search-path](), [uncategorized](), [waiting]() ### AI overview A PostgreSQL patch adds a psql PROMPT variable for displaying the current search_path. The %S substitution works when connected to Postgres 18 or newer, because search_path was first marked as GUC_REPORT in a prior commit. ### Source excerpt On 28th of October 2025, Nathan Bossart committed patch: Add psql PROMPT variable for search_path. The new %S substitution shows the current value of search_path. Note that this only works when connected to Postgres v18 or newer, since search_path was first marked as GUC_REPORT in commit 28a1121fd9. On older versions that don't report search_path, ... Continue reading "Waiting for PostgreSQL 19 - Add psql PROMPT variable for search_path." ## Waiting for PostgreSQL 19 - Support COPY TO for partitioned tables. DevFeed: [Waiting for PostgreSQL 19 - Support COPY TO for partitioned tables.]() Original publisher: [Read original article]() Author: depesz Published: 2025-10-22T10:05:08Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL](), [data]() Tags: [command](), [copy](), [partition](), [partitioning](), [partitions](), [performance](), [pg19](), [postgresql](), [uncategorized](), [waiting]() ### AI overview The article discusses a PostgreSQL patch committed by Masahiko Sawada that adds direct COPY TO support for partitioned tables. Previously, users had to use COPY (SELECT ...) TO as a workaround. The author's test found similar performance, with COPY from a table slightly slower in the reported case. ### Source excerpt On 20th of October 2025, Masahiko Sawada committed patch: Support COPY TO for partitioned tables. Previously, COPY TO command didn't support directly specifying partitioned tables so users had to use COPY (SELECT ...) TO variant. This commit adds direct COPY TO support for partitioned tables, improving both usability and performance. Performance tests show ... Continue reading "Waiting for PostgreSQL 19 - Support COPY TO for partitioned tables." ## Waiting for PostgreSQL 19 - Add IGNORE NULLS/RESPECT NULLS option to Window functions. DevFeed: [Waiting for PostgreSQL 19 - Add IGNORE NULLS/RESPECT NULLS option to Window functions.]() Original publisher: [Read original article]() Author: depesz Published: 2025-10-13T11:13:52Z Content type: article Language: en Sources: [select \* from depesz;]() Topics: [PostgreSQL]() Tags: [first-value](), [functions](), [ignore](), [lag](), [last-value](), [lead](), [nth-value](), [null](), [nulls](), [pg19](), [postgresql](), [uncategorized](), [waiting](), [window](), [window-functions]() ### AI overview The article describes a PostgreSQL patch adding IGNORE NULLS and RESPECT NULLS options, also called a null treatment clause, to the lead, lag, first_value, last_value, and nth_value window functions. IGNORE NULLS skips NULL values, while RESPECT NULLS remains the default behavior. ### Source excerpt On 3rd of October 2025, Tatsuo Ishii committed patch: Add IGNORE NULLS/RESPECT NULLS option to Window functions. Add IGNORE NULLS/RESPECT NULLS option (null treatment clause) to lead, lag, first_value, last_value and nth_value window functions. If unspecified, the default is RESPECT NULLS which includes NULL values in any result calculation. IGNORE NULLS ignores NULL values. ... Continue reading "Waiting for PostgreSQL 19 - Add IGNORE NULLS/RESPECT NULLS option to Window functions." ## 重新思考 Go：了解程序在线上是如何运行的 DevFeed: [重新思考 Go：了解程序在线上是如何运行的]() Original publisher: [Read original article]() Author: Joway Published: 2024-12-10T00:00:00Z Content type: article Language: zh Sources: [Random Thoughts]() Topics: [Go Language](), [Kubernetes](), [cpu](), [cgroups](), [Linux]() Tags: [cgroups](), [cpu](), [go](), [golang](), [k8s](), [linux](), [mechanical-sympathy](), [quota](), [runtime](), [tech](), [waiting]() ### AI overview This article examines how Go programs run in production environments, focusing on the relationship between Kubernetes CPU quotas, physical CPU availability, cgroups, and Go's GOMAXPROCS setting. It explains that CPU quota limits aggregate execution time, while available parallelism can depend on the host's physical cores and the program's design. It also introduces scheduling latency and the factors that affect the computing resources a Go service actually receives. ### Source excerpt 重新思考 Go 系列：这个系列希望结合工作中在 Go 编程与性能优化中遇到过的问题，探讨 Go 在语言哲学、底层实现和现实需求三者之间关系与矛盾。 前言 过去一段时间，在大量的线上服务 case study 过程中，逐步深入了解了如今的业务 Go 进程是如何在一系列繁杂的基础设施之上运行的。有些表现在意料之中，也有一些出乎意料的发现。 ## Skytools3: walmgr DevFeed: [Skytools3: walmgr]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-09-21T15:21:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [Replication](), [Streaming](), [Documentation](), [Monitoring]() Tags: [backup](), [debian](), [documentation](), [postgresql](), [release](), [replication](), [setup](), [standby](), [streaming](), [waiting]() ### AI overview This documentation article introduces Skytools 3 WalMgr, a component for managing PostgreSQL WAL shipping and archiving. It explains preparing a master and standby, taking a base backup, restoring from archives, and using Streaming Replication with PostgreSQL 9.0 and 9.1. ### Source excerpt Let's begin the Skytools 3 documentation effort, which is long overdue. The code is waiting for you over at github, and is stable and working. Why is it still in release candidate status, I hear you asking? Well because it's missing updated documentation. WalMgr is the Skytools component that manages WAL shipping for you, and archiving too. It knows how to prepare your master and standby setup, how to take a base backup and push it to the standby's system, how to archive (at the satndby) master's WAL files as they are produced and have the standby restore from this archive. [Next page]()