[ADMIN] SQLSTATE 53100 could not extend file / disk full

Hello, I wonder whether extra measures are necessary to recover from a disk full error besides freeing enough disk space? It seems that there are enough security measures: http://archives.postgresql.org/message-id/cahhcrepqncn3hoxswaotsj3hjkp5noepb2ky3dfgva4jcxh...@mail.gmail.com Is it no probl

Re: [ADMIN] SQLSTATE 53100 could not extend file / disk full

"Jan-Peter Seifert" wrote: > I wonder whether extra measures are necessary to recover from a > disk full error besides freeing enough disk space? > Is it no problem if the WAL is within the same disk space and > can't be written as well? > Should you free enough disk space, do a checkpoint,

Re: [ADMIN] Very long " in transaction" query

Hi Gnanam, I assume your not ending your transactions with commit or rollback. When using a connection pooler your connection is reused for next request. So if one request does something that initiates an implizit BEGIN (like an UPDATE/INSERT) without a COMMIT or ROLLBACK this connection remai

[ADMIN] Advice/guideline on increasing shared_buffers and kernel parameters

Hi, Our Production server has got 35 GB physical RAM size. Since the server has lots of RAM, we want to really make use of it. We've already configured "max_connections" to 1000 and "shared_buffers" to 1536 MB, but when we tried to increase only "shared_buffers" to 3072MB (keeping "max_connecti