[HACKERS] pgstattuple does not contain CHECK_FOR_INTERRUPTS()

Hi, pgstattuple (and pgstatindex) does not contain CHECK_FOR_INTERRUPTS(). Therefore, we can not stop pgstattuple() by using the signal while a large table is processed. Here is the patch to solve it. Best regards, -- NTT OSS Center Tatsuhito Kasahara diff -cr pgsql/contrib/pgstattuple

Re: [HACKERS] display previous query string of idle-in-transaction

# And I'm going to register this patch on the next commitfest page. -- Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] patch for ja.po

Hi, Honda Shigehiro wrote: > I think this is already patched in cvs of message catalogs. Could you try > psql.po from > http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgtranslation/messages/ja/psql.po I confirmed it. Sorry for the noise. regards, -- Tatsuhito Kasahara kasaha

[HACKERS] patch for ja.po

quot;1 rows" best regards, -- Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp diff -cpr Postgresql-CVS-20090522/src/bin/psql/po/ja.po ja_po_fix/src/bin/psql/po/ja.po *** Postgresql-CVS-20090522/src/bin/psql/po/ja.po 2009-05-22 18:01:22.0 +0900 --- ja_po_fix/src/bin/psql/po/ja.

Re: [HACKERS] display previous query string of idle-in-transaction

hope it would be able to narrowing down problem points more easily. Best regards, -- Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] display previous query string of idle-in-transaction

e of the ways. But I have no specific idea about it now. -- Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] display previous query string of idle-in-transaction

with only " in transaction" message. But if I can also check last query string, I guess which apllication do that and point out the problem point. # As I said, I think a long transaction is not a problem itself. Does that answer your question ? Best regards, -- Tatsuhito Kasahar

Re: [HACKERS] display previous query string of idle-in-transaction

: Using executor hook to get a query string and stores it in shared memory. We can check specified number of query string history. I think I will try mainly 2. # Or this feature may merge to pg_stat_statements. Any comments welcome. Best regards, -- Tatsuhito Kasahara kasahara.tatsuh...@oss

Re: [HACKERS] display previous query string of idle-in-transaction

or not. - check the content of "SOME SQL". best regards, -- Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] display previous query string of idle-in-transaction

current_query --- in transaction [prev]: SELECT * FROM pg_class limit 1; = Thoughts? Best regards. -- Tatsuhito Kasahara kasahara.tatsuh...@oss.ntt.co.jp -- Sent via pgsq

Re: [HACKERS] About a message when "pg_ctl -w start" failed

starting.) > I'd think the right fix is to make it recognize other types of > authentication failures as well. Yes, I agree. I think role and database(postgres) existence check is necessary before starting postmaster. # Or improve the connection test way in test_postmaster_connection(). B

[HACKERS] About a message when "pg_ctl -w start" failed

But, in fact server is already starting. Therefore, users sometimes confuse. I think that if we failed on test_postmaster_connection(), pg_ctl might want to return 0 and show the message like following... "server starting, but could not connect server. Check your authority." Your thoughts? Bes

Re: [HACKERS] PostgreSQL 8.2 : regression failures on IA-64

Hi! I think this was caused by a description mistake of "postgresql-test.patch". > '/SLONY_PGS/PostgreSQL_8.2.0/BUILD/postgresql-8.2.0/src/test/regres/../../../contrib/spi/refint.so > > LANGUAGE C; > CREATE FUNCTION check_foreign_key () > RETURNS trigger > ! AS > '/SLONY_PGS/PostgreSQL