Dear Members!
Windows Clients, PG 9.4 on Linux.
I used [PID + Client IP + Port + BackEnd Start] for unique identification
of a connection.
Every connection store it's unique connection info in a table (per
DataBase).
F.e:
"8574|195.12.4.3|50120|2017-01-01 08:12:15"
Yesterday I realized that BackE
Jeff Janes wrote
> On Wed, Apr 2, 2014 at 12:00 PM, Bala Venkat <
> akpgeek@
> > wrote:
>
>> We are using postgres 9.0. When I looked at the pg_stat_activity table.
>>
>> I have some rows where there is difference of 2 hours between
>> backend_start and xact_start
>>
>> But there is only few m
On Wed, Apr 2, 2014 at 12:00 PM, Bala Venkat wrote:
> We are using postgres 9.0. When I looked at the pg_stat_activity table.
>
> I have some rows where there is difference of 2 hours between
> backend_start and xact_start
>
> But there is only few milli seconds between xact_start and query_sta
Albe Laurenz, 30.07.2009 11:55:
is there a reason why pg_stat_activity is not documented in
the chapter "System Catalogs"?
I guess it is because they are documented in
http://www.postgresql.org/docs/8.4/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE
in Chapter 26.
Maybe a remark in
Thomas Kellerer wrote:
> is there a reason why pg_stat_activity is not documented in
> the chapter "System Catalogs"?
>
> Is this not a "offical" view?
I guess it is because they are documented in
http://www.postgresql.org/docs/8.4/static/monitoring-stats.html#MONITORING-STATS-VIEWS-TABLE
in Ch
Magnus Hagander, 30.07.2009 09:24:
On Thu, Jul 30, 2009 at 08:37, Thomas Kellerer wrote:
Hi,
is there a reason why pg_stat_activity is not documented in the chapter
"System Catalogs"?
Is this not a "offical" view?
It's not a catalog, it's a statistics view. It's documented in "26.2.
The Stati
On Thu, Jul 30, 2009 at 08:37, Thomas Kellerer wrote:
> Hi,
>
> is there a reason why pg_stat_activity is not documented in the chapter
> "System Catalogs"?
> Is this not a "offical" view?
It's not a catalog, it's a statistics view. It's documented in "26.2.
The Statistics Collector", specifically
Hi,
is there a reason why pg_stat_activity is not documented in the chapter "System Catalogs"?
Is this not a "offical" view?
Regards
Thomas
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-ge
2008/12/4 paulo matadr <[EMAIL PROTECTED]>:
> my querys is very biggest ,pg_stat_activity dont show full
> How increase length from pg_stat_activity ?
I don't think you can (easily). You can, however, log long running
queries and that should log the whole thing.
--
Sent via pgsql-general maili
my querys is very biggest ,pg_stat_activity dont show full
How increase length from pg_stat_activity ?
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
On Feb 11, 2008, at 8:14 AM, Alvaro Herrera wrote:
Actually it's not just autovacuum; it's any lazy vacuum. It's hard to
tell those processes apart in pg_stat_activity. Perhaps we could have
added a column in pg_stat_activity indicating processes that don't
hold
old tuples, but I feel that w
Dawid Kuroczko escribió:
> > Dawid Kuroczko escribió:
> > > I'm using 8.3.0 and I see that autovacuum processes in
> > > pg_stat_activity have xact_start.
> > >
> > > As far as I know, since at least 8.2.x the VACUUM does not start a new
> > > transaction.
> I am referrring to the E.8.3.5 Release
On Feb 11, 2008 2:27 PM, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> Dawid Kuroczko escribió:
> > I'm using 8.3.0 and I see that autovacuum processes in
> > pg_stat_activity have xact_start.
> >
> > As far as I know, since at least 8.2.x the VACUUM does not start a new
> > transaction.
> > If that
Dawid Kuroczko escribió:
> I'm using 8.3.0 and I see that autovacuum processes in
> pg_stat_activity have xact_start.
>
> As far as I know, since at least 8.2.x the VACUUM does not start a new
> transaction.
> If that statement is correct, the xact_start column in
> pg_stat_activity should be NUL
Hello.
I'm using 8.3.0 and I see that autovacuum processes in
pg_stat_activity have xact_start.
As far as I know, since at least 8.2.x the VACUUM does not start a new
transaction.
If that statement is correct, the xact_start column in
pg_stat_activity should be NULL...
Why does it matter? Monit
That was it. (not having it turned on. duh).
Guess I should have read section 23.2 of the docs..."The Statistics
Collector"
Thanks for the heads up.
Jeff
Tom Lane wrote:
Jeff Amiel <[EMAIL PROTECTED]> writes:
however, if I checked pg_stat_activity during the same time period, I
saw nothing
Jeff Amiel <[EMAIL PROTECTED]> writes:
> however, if I checked pg_stat_activity during the same time period, I
> saw nothing populated in the current_query column...ever.
Did you have it turned on? (stats_command_string config parameter)
Were you checking as superuser?
I ran a home-grown self continuous stress test tool against my 7.4.2
database.
I banged 'ps' (running freebsd) while it was active and witnessed
several of the 'back end' postgres processes exeucting queries, commits,
inserts, etc(the actual work the processes were doing was listed in
the
Hi all,
in the pg_stat_activity catalog there is a field called current_query but it
is in blank when i modify the
show statement stat in postgresql.conf i win nothing. what am i doing wrong?
thanks in advance,
Jaime Casanova (el_vigia)
___
19 matches
Mail list logo
