> Here is a debug (level 2) output - does this help any
> more?... If not, what should I provide for you in terms of
> debugging?...
Hmm. I didn't find the update/select combination you specified in your
problem statement in your debugging output, but it wouldn't have likely
helped anywa
Here is a debug (level 2) output - does this help any
more?... If not, what should I provide for you in terms of
debugging?...
FindExec: found "/usr/local/postgres/bin/postgres" using argv[0]
binding ShmemCreate(key=52e2c1, size=1104896)
DEBUG: Data Base System is starting up at Wed Oc
Sean Kelly <[EMAIL PROTECTED]> writes:
>> This backend crash should have left a core file in your database
>> directory (PGDATA/base/users/core). Can you provide a backtrace
>> from that corefile using gdb?
> No core there ... any other suggestions?
You probably started the postmaster wit
Andreas Hinz ([EMAIL PROTECTED]) reports a bug with a severity of 4
The lower the number the more severe it is.
Short Description
Slack7.1/linux.2.4 compile error: storage size of `semun' isn't known
Long Description
Hi,
I have a the following error compiling latest CVS of PostgreSQL:
ipc.c: In
On Tue, 17 Oct 2000, Tom Lane wrote:
> PrivateRefCount is local to a particular backend, so the behavior of
> other clients shouldn't matter (in theory anyway ;-)). It should be
> sufficient to reproduce the sequence executed by your specific session.
> Not that that helps much if you don't re
[EMAIL PROTECTED] writes:
> I have a the following error compiling latest CVS of PostgreSQL:
Odd. Is configure defining HAVE_SYS_SEM_H in src/include/config.h?
What was the last version you compiled successfully?
> Removing "void *__pad;" from the above makes the compile finish.
That doesn't
Hi my name is Sylvain
I use Postgres 6.5.3-3
Why is the pg_log???
I have a program than run 24hrs/day and many transaction has been send
to postgres
eg (select, insert, update, vacuum, (begin work-commit work)...)
At begin, with a new database the pg_log are 40k
After many days my pg_log is come
I'm not sure if this is a reported bug or not. SELECT statements with some
aggregates on certain complex views can give terrible results. An example:
CREATE TABLE master (
id int4 not null,
no int4 check (no >= 0) default 0,
primary key (id, no),
started date check ((not started i
Kovacs Zoltan Sandor <[EMAIL PROTECTED]> writes:
> I'm not sure if this is a reported bug or not. SELECT statements with some
> aggregates on certain complex views can give terrible results. An example:
Aggregates on grouped views do not and cannot work in 7.0 or earlier
releases, because the exi
[EMAIL PROTECTED] writes:
> users=> update users_tbl set added=TRUE where username like 'neta%';
> pqReadData() -- backend closed the channel unexpectedly.
> bash$ tail ~postgres/server.log
> Server process (pid 23747) exited with status 11 at Tue Oct 24 13:52:29 2000
This backend crash should h
On Wed, 25 Oct 2000 12:52:44 -0400, Tom Lane said:
> [EMAIL PROTECTED] writes:
> > users=> update users_tbl set added=TRUE where username like 'neta%';
> > pqReadData() -- backend closed the channel unexpectedly.
>
> > bash$ tail ~postgres/server.log
> > Server process (pid 23747) exited wi
11 matches
Mail list logo
