> On Feb 12, 2015, at 3:21 PM, Day, David wrote:
>
> Update/Information sharing on my pursuit of segmentation faults
>
> FreeBSD 10.0-RELEASE-p12 amd64
> Postgres version 9.3.5
>
> Below are three postgres core files generated from two different machine (
> Georgia and Alabama ) on Feb 11.
On Apr 9, 2014, at 3:40 PM, CS_DBA wrote:
> Hi All;
>
> We have a client with this requirement:
>
> At rest data must be encrypted with a unique client key
>
> Any thoughts on how to pull this off for PostgreSQL stored data?
Does there happen to be a Postgresql proxy, such as a modified pgbou
On Aug 15, 2013, at 5:41 AM, Stuart Ford wrote:
> Dear community
>
> We have a problem on our development database server, which supports a PHP
> application, which connects to it from a different server. Sometimes,
> around 1 in 4 page loads, it fails and reports the following error message:
>
On May 10, 2012, at 4:31 AM, Horaci Macias wrote:
> Hi everybody,
>
> I'm running postgres 9.1 and having disk space problems.
> My application captures information 24x7 and stores it into the database.
> This includes several bytea and can be ~5M entries a day, so the size can be
> an issue af
d of day /
> start of day time.
> Anyway, worth a thought for sure so thanks.
>
> H
>
> On 10/05/12 16:42, Guy Helmer wrote:
>> On May 10, 2012, at 4:31 AM, Horaci Macias wrote:
>>
>>> Hi everybody,
>>>
>>> I'm running postgres
Tom Lane wrote:
Guy Helmer writes:
Tom Lane wrote:
Normally I'd say "data corruption", but it is odd if you got the
identical message from two different machines. Can you reproduce
it with a debugger attached? If so, a backtrace from the call of
errfinish
Tom Lane wrote:
Guy Helmer writes:
On systems running Postgresql 8.3.6, I have a nightly backup using
pg_dump that failed on two machines overnight with this error:
pg_dump: SQL command failed
pg_dump: Error message from server: ERROR: invalid memory alloc request size
emory errors. Since this happened simultaneously on two separate
machines, I would not expect these issues to be likely causes.
Any suggestions?
Thanks,
Guy Helmer
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresq
