| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | imchifan8(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19879: Blocked COPY FROM reports NULL command and type in pg_stat_progress_copy |
| Date: | 2026-11-20 22:35:41 |
| Message-ID: | CAD21AoBD2=R3esjqjbnt28H5E3SDW_PwBqc2qeTKndph+cskaA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wed, Nov 11, 2026 at 6:00 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 19879
> Logged by: Noah
> Email address: imchifan8(at)gmail(dot)com
> PostgreSQL version: 18.6
> Operating system: Linux/amd64
> Description:
>
> A server-side COPY FROM that blocks while opening a FIFO appears in
> pg_stat_progress_copy with the correct relation OID but NULL command and
> type. The view should identify the running command as COPY FROM and its I/O
> type as FILE, as documented for pg_stat_progress_copy.
>
> How to repeat:
>
> Save this as run.sh:
>
> #!/usr/bin/env bash
> set -euo pipefail
>
> : "${PG_BINDIR:?set PG_BINDIR to the target PostgreSQL bin directory}"
> base="$PWD/work"
> data="$base/data"
> sock="$base/socket"
> fifo="$base/input.fifo"
> mkdir -p "$base" "$sock"
> "$PG_BINDIR/initdb" -D "$data" --no-locale --encoding=UTF8 >/dev/null
> "$PG_BINDIR/pg_ctl" -D "$data" -o "-k $sock -c listen_addresses=''" -w start
> >/dev/null
> cleanup() {
> "$PG_BINDIR/pg_ctl" -D "$data" -m immediate -w stop >/dev/null 2>&1 ||
> true
> }
> trap cleanup EXIT
> "$PG_BINDIR/psql" -X -h "$sock" -d postgres -v ON_ERROR_STOP=1 -c 'CREATE
> TABLE copy_progress_target(i int)'
> mkfifo "$fifo"
> "$PG_BINDIR/psql" -X -h "$sock" -d postgres -v ON_ERROR_STOP=1 \
> -c "COPY copy_progress_target FROM '$fifo'" >"$base/copy.out"
> 2>"$base/copy.err" &
> copy_pid=$!
> for _ in $(seq 1 100); do
> row=$("$PG_BINDIR/psql" -XAt -h "$sock" -d postgres -c \
> "SELECT coalesce(command,'<NULL>') || '|' || coalesce(type,'<NULL>')
> FROM pg_stat_progress_copy WHERE relid='copy_progress_target'::regclass")
> test -n "$row" && break
> sleep 0.05
> done
> printf 'observed=%s\n' "$row"
> printf '1\n' >"$fifo"
> wait "$copy_pid"
> test "$row" = 'COPY FROM|FILE'
Thank you for the report and the patch.
Since the progress information is updated incrementally as the command
proceeds, I think it's expected that the view doesn't show complete
information at some point. Even while the command and type columns are
NULL, the COPY already appears in pg_stat_progress_copy with its pid
and relid, so users can find which command the backend is stuck on. So
I don't think it's worth fixing. BTW how did you find this problem?
Regards,
--
Masahiko Sawada
Amazon Web Services: https://aws.amazon.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-11-20 22:47:40 | Re: BUG #19924: unrecognized node type in create_plan_recurse: UNION, LIMIT, json_populate_recordset, inheritance |
| Previous Message | Jan Nidzwetzki | 2026-11-20 22:33:35 | Re: pg_rewind and hint bits leads to visibility corruption |