Lokendra Dixit lokendra.di...@rmsi.com wrote:
RAM: 2 GB
You do realize how small that is for a database server, I hope.
Many people are walking around with cell phones in their pockets
that have a lot more. This could contribute to severe slowdown with
even minimal growth of the database,
The following bug has been logged on the website:
Bug reference: 7521
Logged by: Boy de Laat
Email address: b...@atsc.nl
PostgreSQL version: 9.1.4
Operating system: CentOS 6.2 x86_64
Description:
I've setup some slave replication and just to be sure i use pg_dump as
Hi,
On 03/09/2012 18:06, Tom Lane wrote:
pgm...@joh.to writes:
We had a segmentation fault in PostgreSQL 9.1.5 with PL/PerlU.
...
It seems to have happened when a PL/PerlU executed a prepared statement
which calls another PL/PerlU function.
Hm. Is it possible that the prepared statement
On 9/4/12 2:22 PM, Murray Cumming wrote:
On Tue, 2012-09-04 at 10:31 -0400, Tom Lane wrote:
murr...@murrayc.com writes:
At some point, probably in 9.1.5, the -k option to Postgres (Unix-domain
socket location in --help), stopped accepting paths that contain spaces.
For instance,
-k
Peter Eisentraut pete...@gmx.net writes:
Maybe it would be easier if multiple -k options accumulated.
Hm, interesting thought, but how would we make that play in the generic
GUC support? Or are you imagining that we'd just kluge up -k with some
single-purpose code?
Peter Eisentraut pete...@gmx.net writes:
Maybe it would be easier if multiple -k options accumulated.
After further thought I'm not very enamored of that concept. We've made
considerable compromises to ensure that every postmaster command-line
option corresponds exactly to some GUC parameter;
