pg.ddx.io pgsql-committers@postgresql.org mailing list archive
help / color / mirror / Atom feedpgsql: Add agg/normal/trigger/window flags for psql \df and in \df
2+ messages / 2 participants
[nested] [flat]
* pgsql: Add agg/normal/trigger/window flags for psql \df and in \df
@ 2009-04-21 15:49 Bruce Momjian <momjian@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: momjian@postgresql.org @ 2009-04-21 15:49 UTC (permalink / raw)
To: pgsql-committers
Log Message:
-----------
Add agg/normal/trigger/window flags for psql \df and in \df output.
David Fetter
Modified Files:
--------------
pgsql/doc/src/sgml/ref:
psql-ref.sgml (r1.223 -> r1.224)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/psql-ref.sgml?r1=1.223&r2=1.224)
pgsql/src/bin/psql:
command.c (r1.204 -> r1.205)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c?r1=1.204&r2=1.205)
describe.c (r1.208 -> r1.209)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.c?r1=1.208&r2=1.209)
describe.h (r1.39 -> r1.40)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/describe.h?r1=1.39&r2=1.40)
help.c (r1.146 -> r1.147)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/help.c?r1=1.146&r2=1.147)
pgsql/src/test/regress/expected:
polymorphism.out (r1.19 -> r1.20)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/polymorphism.out?r1=1.19&am...)
^ permalink raw reply [nested|flat] 2+ messages in thread
* pgsql: Continue my quest to make 002_blocks.pl pass reliably.
@ 2024-02-01 16:56 Robert Haas <rhaas@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Robert Haas @ 2024-02-01 16:56 UTC (permalink / raw)
To: pgsql-committers@lists.postgresql.org
Continue my quest to make 002_blocks.pl pass reliably.
The latest buildfarm failures show that after the insert, we don't
actually wait long enough for WAL summarization to catch up, apparently
because the on disk state gets updated before the in-memory state, and
so by checking the on disk state to see whether we're caught up and then
the in-memory state to see where exactly how far we've progressed, we
can, if unlucky, derive an older value of summarized_lsn, messing up
the rest of the test.
Attempt to fix this by using pg_available_wal_summaries() everywhere in
the test and pg_get_wal_summarizer_state() nowhere.
Per buildfarm.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/19a829a3270fb083b3d6ae967cd3b3c02a170a38
Modified Files
--------------
src/bin/pg_walsummary/t/002_blocks.pl | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-02-01 16:56 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2009-04-21 15:49 pgsql: Add agg/normal/trigger/window flags for psql \df and in \df Bruce Momjian <momjian@postgresql.org>
2024-02-01 16:56 pgsql: Continue my quest to make 002_blocks.pl pass reliably. Robert Haas <rhaas@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox