Hello,
We used postgres since 5 months, and we have some times crash, with the
following entry in the postgres.log:
/usr/lib/postgresql/bin/postmaster: ServerLoop: select failed: No child
processes
Please help me...
Here some informations on the installation:
Debian 2.2.17
Postgres 7.0.3
Best
Jonas Bengtsson wrote:
>
> Can't you do a dump with the oid's?
>
> But when I want to know the primary key of the inserted row
> I have to do an extra select query. If I use oid I just use
> pg_getlastoid() in php.
> And it is redundant data to store another integer.
>
> Comments?
I have often
Christian Marschalek wrote:
> Hi all of you! :o)
>
> I guess I do have to shut down the database before shutting down the
> linux box?
> How would I accomplish this?
> Just by killing the postmaster per pid?
>
> Tia and regards!
>
>
> ---(end of broadcast)-
> Seems Mandrake Linux is not the only platform where roundoff behavior is
> less IEEE-perfect than Thomas would like it to be. Perhaps we need a
> slightly more robust approach to controlling roundoff error.
Go ahead. istm that asking modulo, trunc, etc to Do The Right Thing is
not a big deal,
On Friday, March, 2001-03-23 at 17:42:37, Tom Lane wrote:
> "Matt Friedman" <[EMAIL PROTECTED]> writes:
> > I currently running vacuum nighly using cron and once in a while I run
> > vacuum analyze (as postgres).
> > Any reason why I wouldn't just simply run vacuum analyze each night?
>
> If you
Bill Barnes <[EMAIL PROTECTED]> writes:
> Install in Mandrake 7.2 gives me an error message:
> In file included from pgtkAppInit.c:15:
> /usr/include/tk.h:83: X11/Xlib.h: No such file or
> directory
I'd guess that that file is available in some X-programming devel RPM or
other. Possibly you cou
FATAL 1: cannot open /usr/local/pgsql/data/PG_VERSION: Too many open files in s
ystem
postmaster: streamconnection: accept: too many open files in system
the last message is repeating for some minutes, then comes this:
postmaster: StreamConnection: accept: Too many open files in system
postma
Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> So I'll use "lock table" (this time in exclusive mode :) ), then select for
> update, then insert|update and leave the unique index to trigger an error
> when I forget to all that correctly, in which case it's definitely an error.
If you're holding an e
Well I think I can do it without updating...
Thanks to both of you :o)
> -Original Message-
> From: Richard Huxton [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, March 25, 2001 2:14 PM
> To: Brett W. McCoy
> Cc: Christian Marschalek; [GENERAL] PostgreSQL
> Subject: Re: [GENERAL] Views...
>
"Brett W. McCoy" wrote:
>
> Briefly, a view is a 'virtual' table -- you create a view with a select
> statement that can relate data between different tables or use a subset of
> data from a specific table. You can think of them as a 'saved query'.
> Once you create a view, you can then query th
At 12:59 PM 3/24/01 -0500, Tom Lane wrote:
>Lincoln Yeoh <[EMAIL PROTECTED]> writes:
>> Is it technically possible for there to be a "select for insert"? e.g.
>> other select for inserts with the same effective where clause will block
>> even if no rows are there yet.
>
>What would you define as
11 matches
Mail list logo
