"Tena Sakai" <[EMAIL PROTECTED]> writes:
> I have an application that emits query to postgres
> (running v 8.2.4 on Dell Hardware/Redhat enterprise
> server) and I want to look at what postgres receives.
Turn on query logging (log_statement)?
regards, tom lane
---
Hi everybody,
I have an application that emits query to postgres
(running v 8.2.4 on Dell Hardware/Redhat enterprise
server) and I want to look at what postgres receives.
The only way I know to do so is to run a view called
pg_stat_activity, which gives me a column called
current_query. It so ha
I have installed postgres 8.2.4 in my development environment. I have
the stats_command_string, stats_start_collector, stats_block_level,
stats_row_level options turned on in postgresql.conf file but still the
pg_statio_user_tables view does not get populated. Is there any other
option I need to en
Hi,
Thomas Karcher <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > this one is still open when I run pg_stop_backup(), so I want to trigger
the
> > archive_command to be sure that I don't miss anything.
>
> I guess what you want is pg_switch_xlog() (see
> http://www.postgresql.org/docs/8.2/static/fun
"Peter Koczan" <[EMAIL PROTECTED]> writes:
> I'm looking into adding things to the way I monitor pgsql
> installations. One of them was free space map stuff. Is there a way to
> get free space information (especially used free space) without having
> to screen-scrape the output of VACUUM VERBOSE?
Hi,
> this one is still open when I run pg_stop_backup(), so I want to trigger the
> archive_command to be sure that I don't miss anything.
I guess what you want is pg_switch_xlog() (see
http://www.postgresql.org/docs/8.2/static/functions-admin.html)
which became available with PG 8.2 ...
Tho
Hi all,
I'm looking into adding things to the way I monitor pgsql
installations. One of them was free space map stuff. Is there a way to
get free space information (especially used free space) without having
to screen-scrape the output of VACUUM VERBOSE? I know you can get the
allocated fsm pages
Hi,
I want to do online backup saving the WAL files. So I set the database into
backup mode, make a backup, and then set the datbase to normal mode with
pg_stop_backup().
To make the backup complete, I need to backup the actual WAL file too, but
this one is still open when I run pg_stop_backup
