Zitat von Andrew Sullivan <[EMAIL PROTECTED]>:
On Mon, Dec 10, 2007 at 04:26:12PM +0100, Listaccount wrote:
Hello
I have been trapped by the advice from the manual to use "sysctl -w
vm.overcommit_memory=2" when using Linux (see 16.4.3. Linux Memory
Overcommit). This value should only be used w
Hi
I am unable to start Postgres on Windows XP machine using following
command:
pg_ctl start -D "D:\Platform\DevEnv\PostgreSQL\8.2\data\"
The error message displayed is:
pg_ctl: another server might be running; trying to start server anyway
2007-12-11 14:42:31 PANIC: could not open contro
* Andrew Sullivan:
> You _want_ the fork to fail when the kernel can't (over)commit the
> memory, because otherwise the stupid genius kernel will come along
> and maybe blip your postmaster on the head, causing it to die by
> surprise.
The other side of the story is that with overcommit, the mach
Hi,
I am writing a PL/SQL script to process data from a high dimensionality table
where this table has most of it's field names encapsulating data. I would like
to automatically loop through the fields of a RECORD variable (returned from a
cursor) obtaining the field name and the field value.
F
On Tue, Dec 11, 2007 at 09:23:38AM +0100, Listaccount wrote:
> I don't want to start the discussion what is the rigth thing todo,
Then you shouldn't ask here. The manual was changed to say what it does
after considerable community discussion. In my view, the Linux kernel's
behaviour is complet
Zitat von Andrew Sullivan <[EMAIL PROTECTED]>:
On Tue, Dec 11, 2007 at 09:23:38AM +0100, Listaccount wrote:
I don't want to start the discussion what is the rigth thing todo,
Then you shouldn't ask here. The manual was changed to say what it does
after considerable community discussion. In
Listaccount wrote:
> I would have not been surprised if the OOM-Killer would go around in case
> of short memory but i was surprised to see fork failed with a system having
> 1GB Memory available.
We've had *a lot* of problem reports due to the OOM killer.
--
Alvaro Herrera
On Tue, Dec 11, 2007 at 03:08:36PM +0100, Listaccount wrote:
> I would have not been surprised if the OOM-Killer would go around in
> case of short memory but i was surprised to see fork failed with a
> system having 1GB Memory available.
You don't understand: the system _did not_ have 1G of m
Hi people,
I have a case and I got a doubt what should be the
best ways.
One table has more than 150 million of rows, and I
thought that could divided by state.
For each row has person ID, state and other
informations, but the search would be done only by
person ID (number column).
I can improve
I posted a topic in general but I was told to post it here I need to be able
to run pgagent on a mac the problem we are having is getting a daemon to run
on a mac
if anyone can help please tell me were I can get a daemon to run on the mac
we have tried the unix daemon but cannot get that to ins
Hi. You could do a query to the system catalogs (pg_attribute, for example)
with your table name as the search criteria and the field names as the data;
loop through that data to create your query in a string variable, and then
EXECUTE it. While you are "looping" through the results of the system
c
> No, pg_dump isn't involved --- the new smarts are inside the server,
> in CREATE CONSTRAINT TRIGGER. It sounds like Peter has a case that is
> confusing that new code. Could we see a complete example?
Sure, here's the command:
$ /s/postgresql-8.2.5/bin/pg_dump -h sensei -p 5432 -C -Fc sushi |
"Peter Koczan" <[EMAIL PROTECTED]> writes:
>> No, pg_dump isn't involved --- the new smarts are inside the server,
>> in CREATE CONSTRAINT TRIGGER. It sounds like Peter has a case that is
>> confusing that new code. Could we see a complete example?
> Sure, here's the command:
[ squint... ] Whi
What windows login account are you using? Probably use the Postgres login
account.
Subject: [ADMIN] Postgres StartDate: Tue, 11 Dec 2007 17:16:23 +0800From:
[EMAIL PROTECTED]: pgsql-admin@postgresql.org
Hi
I am unable to start Postgres on Windows XP machine using following command:
pg_c
Kindly post your query on [EMAIL PROTECTED] as that would be the right place
for PgAdmin and PgAgent.
> From: [EMAIL PROTECTED]> Subject: [ADMIN] pgagent on a mac> Date: Wed, 12 Dec
> 2007 13:17:57 +1200> To: pgsql-admin@postgresql.org> > I posted a topic in
> general but I was told to post i
We were running into problems today when we tried to import a 8.2.4 dump
in a 8.1.5 database. It had to do with the new way of assigning
sequences to colums, which confused 8.1.5 I didn't expect that at the
time of configuration, and currently is down-grading to 8.1.x not an
easy option anymore.
I
Wouter Pels wrote:
We were running into problems today when we tried to import a 8.2.4 dump
in a 8.1.5 database. It had to do with the new way of assigning
sequences to colums, which confused 8.1.5 I didn't expect that at the
time of configuration, and currently is down-grading to 8.1.x not an
ea
17 matches
Mail list logo
