ms that vacuum could not
delete old clog files at all.
My configurations are as follows:
- - - -
tcpip_socket = true
max_connections = 500
port = 5432
shared_buffers = 1000
syslog = 2
log_min_messages = fatal
#others are default values.
- - - -
Thanks
Duan
> Duan Ligong wrote:
>
> >
ust killing the processes?
#It seems that the 7 rows are caused by logining db and executing
the select clause. and they are not long-running transactions, aren't
they? because the procpid changes when I logout and login again.
Thanks
Duan
> --- On Thu, 9/4/08, Duan Ligong <[EMAIL
Thanks for your reply.
Greg wrote:
> On Tue, 2 Sep 2008, Duan Ligong wrote:
> > - Does Vacuum delete the old clog files?
>
> Yes, if those transactions are all done. One possibility here is that
> you've got some really long-running transaction floating around that is
Alvaro Herrera wrote:
> > Duan Ligong wrote:
> > I have encountered an issue that there are too many
> > clog file under the .../pg_clog/ directory. Some of them
> > were even produced one month ago.
>
> If you're going to repost a question, it is only po
Hi, there.
I have encountered an issue that there are too many
clog file under the .../pg_clog/ directory. Some of them
were even produced one month ago.
My questions:
- Does Vacuum delete the old clog files?
- Can we controll the maximum number of the clog files?
- When, or in what case is a
ed by external
programs?
Best regards
Duan
> --
> Alvaro Herrerahttp://www.CommandPrompt.com/
> The PostgreSQL Company - Command Prompt, Inc.
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make ch
Hi,
Would you like to be so kind as to answer the following questions:
- Is there any way to control the number of clog files and xlog files?
I encounter an issue that there are too many clog files under the
pg_clog/ directory which occupy more space than I can endure..
- What determines the
