From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | amit(dot)kapila16(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Inconsistency between pg_stat_activity and log_duration |
Date: | 2014-02-07 23:31:47 |
Message-ID: | 20140208.083147.7144463289061930.t-ishii@sraoss.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>> The query is piggy backed on the same connection to PostgreSQL opend
>> by user (pgpool-II cannot issue "sync" because it closes the
>> transaction, which in turn closes user's unnamed portal).
>
> This argument (and usage) seems pretty broken. If you don't issue
> sync then how do you know you've gotten all of the command's output?
>
> If you're issuing a flush instead, maybe we could consider whether it's
> reasonable to do an extra pgstat_report_activity() upon receipt of a
> flush message. But -1 for putting it into the normal control flow.
Pgpool-II issues "flush" of course.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-02-07 23:43:11 | Re: Changeset Extraction v7.5 |
Previous Message | Erik Rijkers | 2014-02-07 21:32:45 | Re: Changeset Extraction v7.5 |