Enrico Pirozzi wrote:
> I have a new postgresql 9.5.0 installation on a new virtual server debian 8.3
> x64 with 4gb RAM, I have
> compiled postgresql from source.
>
> When I import a dump with materialized views I see that postgres process
> takes about all 4 Gb and then
> I have this error
>
Hi
I have a new postgresql 9.5.0 installation on a new virtual server debian
8.3 x64 with 4gb RAM, I have compiled postgresql from source.
When I import a dump with materialized views I see that postgres process
takes about all 4 Gb and then I have this error
fork: Cannot allocate memory
Can a
Hi,
On Wed, 02 Jul 2008, Tom Lane <[EMAIL PROTECTED]> writes:
> Are there any foreign keys referencing this table? If so, you're
> probably running out of memory for the list of pending trigger events
> (to verify that the FK constraint isn't violated by the delete).
>
> Allowing the triggers to
Volkan YAZICI <[EMAIL PROTECTED]> writes:
> We have an IBM System x3850 machine running on RHEL 4.5 Cluster Suite
> with high-availability enabled. During a huge delete process, PostgreSQL
> (8.3.1) exhausts available memory and receives an OOM kill.
Are there any foreign keys referencing this tab
Hi,
We have an IBM System x3850 machine running on RHEL 4.5 Cluster Suite
with high-availability enabled. During a huge delete process, PostgreSQL
(8.3.1) exhausts available memory and receives an OOM kill.
$ /srv/usr/bin/psql -e -f
~/schemas/working/test_1_5_1_0-schema-delete-bogus-2-20080625
