pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgre Server stopped during continuous run.
3+ messages / 3 participants
[nested] [flat]
* Postgre Server stopped during continuous run.
@ 2010-06-21 10:52 Vishnu S. <vishnu.s@nestgroup.net>
2010-06-21 19:03 ` Re: Postgre Server stopped during continuous run. Devrim GÜNDÜZ <devrim@gunduz.org>
2010-06-21 20:11 ` Re: Postgre Server stopped during continuous run. Kevin Grittner <Kevin.Grittner@wicourts.gov>
0 siblings, 2 replies; 3+ messages in thread
From: Vishnu S. @ 2010-06-21 10:52 UTC (permalink / raw)
To: pgsql-admin
Hi,
I am new in PostgreSQL database.
I have a continuous running application that uses PostgreSQL as
database. This application inserts about 20 MB data into the database in
every second.I have disabled the WAL log , because all the data
inserting into the database is logged in the WAL files, that takes so
much space in the disc. My issue is that , after a two days continuous
run the Postgres server stopped unexpectedly . Can you explain what is
the reason behind this.? How can we recover from this. How can we use
Postgres database effectively in a continuous running application. Can
we specify the maximum size of WAL file that can be stored in the
database.On reaching the specified limit the older log files can be
deleted automatically.
Thanks & Regards,
Vishnu S
***** Confidentiality Statement/Disclaimer *****
This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt.
The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Postgre Server stopped during continuous run.
2010-06-21 10:52 Postgre Server stopped during continuous run. Vishnu S. <vishnu.s@nestgroup.net>
@ 2010-06-21 19:03 ` Devrim GÜNDÜZ <devrim@gunduz.org>
1 sibling, 0 replies; 3+ messages in thread
From: Devrim GÜNDÜZ @ 2010-06-21 19:03 UTC (permalink / raw)
To: Vishnu S. <vishnu.s@nestgroup.net>; +Cc: pgsql-admin
On Mon, 2010-06-21 at 16:22 +0530, Vishnu S. wrote:
> I have disabled the WAL log ,
What?
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org Twitter: http://twitter.com/devrimgunduz
Attachments:
signature.asc (application/pgp-signature, 197B) download
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Postgre Server stopped during continuous run.
2010-06-21 10:52 Postgre Server stopped during continuous run. Vishnu S. <vishnu.s@nestgroup.net>
@ 2010-06-21 20:11 ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
1 sibling, 0 replies; 3+ messages in thread
From: Kevin Grittner @ 2010-06-21 20:11 UTC (permalink / raw)
To: Vishnu S. <vishnu.s@nestgroup.net>; pgsql-admin
"Vishnu S." <vishnu.s@nestgroup.net> wrote:
> I have disabled the WAL log
Exactly what did you do to accomplish that?
> the Postgres server stopped unexpectedly . Can you explain what
> is the reason behind this.?
Can you show us the error messages from the server log and the user
connections around the time of failure?
> Can we specify the maximum size of WAL file that can be stored in
> the database. On reaching the specified limit the older log files
> can be deleted automatically.
The default is to use very little WAL file space, but it's
configurable based on checkpoint_segments. What you're describing
sounds like it *might* be caused by turning on archiving, but having
an archive_command which returns a failure exit code. That would
keep the files indefinitely on the assumption that you want to fix
your archiving. The solution is to turn off archiving or fix your
archive command.
For ideas on what information you can include in your post to allow
us to better understand your situation and provide more helpful
advice, please see this page:
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
In particular, knowing what version of PostgreSQL you are running in
what environment, the error messages you got, the contents of the
postgresql.conf file (without the comments), and the steps you took
which led up to the problem would be the most likely to give us
enough to be more helpful.
-Kevin
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2010-06-21 20:11 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2010-06-21 10:52 Postgre Server stopped during continuous run. Vishnu S. <vishnu.s@nestgroup.net>
2010-06-21 19:03 ` Devrim GÜNDÜZ <devrim@gunduz.org>
2010-06-21 20:11 ` Kevin Grittner <Kevin.Grittner@wicourts.gov>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox