Re: pgsql: Convert debug message from ereport to elog

Just out of curiosity, what is the reason why you did this? I guess using elog instead of ereport for debugging message is preferable, while for non debugging messages using ereport is preferable, but actually sometimes elog is used for error messages in the file. Best regards, -- Tatsuo Ishii SR

pgsql: Exclude files in .git from list of perl files

Exclude files in .git from list of perl files The .git directory might contain perl files, as hooks, for example. Since we have no control over these they should be excluded from things like our perlcritic checks. Per offline report from Mike Blackwell. Branch -- master Details --- http

pgsql: Fix bugs in vacuum of shared rels, by keeping their relcache ent

Fix bugs in vacuum of shared rels, by keeping their relcache entries current. When vacuum processes a relation it uses the corresponding relcache entry's relfrozenxid / relminmxid as a cutoff for when to remove tuples etc. Unfortunately for nailed relations (i.e. critical system catalogs) bugs cou

pgsql: Fix bugs in vacuum of shared rels, by keeping their relcache ent

Fix bugs in vacuum of shared rels, by keeping their relcache entries current. When vacuum processes a relation it uses the corresponding relcache entry's relfrozenxid / relminmxid as a cutoff for when to remove tuples etc. Unfortunately for nailed relations (i.e. critical system catalogs) bugs cou

pgsql: Fix bugs in vacuum of shared rels, by keeping their relcache ent

Fix bugs in vacuum of shared rels, by keeping their relcache entries current. When vacuum processes a relation it uses the corresponding relcache entry's relfrozenxid / relminmxid as a cutoff for when to remove tuples etc. Unfortunately for nailed relations (i.e. critical system catalogs) bugs cou

pgsql: Fix bugs in vacuum of shared rels, by keeping their relcache ent

Fix bugs in vacuum of shared rels, by keeping their relcache entries current. When vacuum processes a relation it uses the corresponding relcache entry's relfrozenxid / relminmxid as a cutoff for when to remove tuples etc. Unfortunately for nailed relations (i.e. critical system catalogs) bugs cou

pgsql: Fix bugs in vacuum of shared rels, by keeping their relcache ent

Fix bugs in vacuum of shared rels, by keeping their relcache entries current. When vacuum processes a relation it uses the corresponding relcache entry's relfrozenxid / relminmxid as a cutoff for when to remove tuples etc. Unfortunately for nailed relations (i.e. critical system catalogs) bugs cou

pgsql: Fix bugs in vacuum of shared rels, by keeping their relcache ent

Fix bugs in vacuum of shared rels, by keeping their relcache entries current. When vacuum processes a relation it uses the corresponding relcache entry's relfrozenxid / relminmxid as a cutoff for when to remove tuples etc. Unfortunately for nailed relations (i.e. critical system catalogs) bugs cou

pgsql: Convert debug message from ereport to elog

Convert debug message from ereport to elog Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/8a07ebb3c172374aa2c83df61c4e05c059511c9a Modified Files -- src/backend/replication/logical/worker.c | 8 1 file changed, 4 insertions(+), 4 deletions(-)

pgsql: doc: Replace non-ASCII lines in psql example output

doc: Replace non-ASCII lines in psql example output We normally use the default line mode in examples. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b5d099f82ae6e7c49c397bd85832f13729626035 Modified Files -- doc/src/sgml/jit.sgml | 44