Hi,
We have problems with backend processes that close the channel because of
palloc() failures. When an INSERT statement fails, the backend reports an
error (e.g. `Cannot insert a duplicate key into a unique index') and
allocates a few bytes more memory. The next SQL statement that fails
causes
A bug report on this was filled out against the 6.3 release as well.
Don't know the status of it, however :(
Mirko Kaffka wrote:
>
> Hi,
>
> We have problems with backend processes that close the channel because of
> palloc() failures. When an INSERT statement fails, the backend reports an
> er
I've been having some intermittent problems with PostgreSQL, both versions
6.4.2 and 6.5b1. I use a bash shell script run as a cron job to restart the
postmaster if it dies. Sometimes the cron job reports the following error
message:
*ap++ == 0x55
Tell bgahl@kd6kmx to fix this someday.
Stopping m
Mirko Kaffka <[EMAIL PROTECTED]> writes:
> We have problems with backend processes that close the channel because of
> palloc() failures. When an INSERT statement fails, the backend reports an
> error (e.g. `Cannot insert a duplicate key into a unique index') and
> allocates a few bytes more memor
>
> Mirko Kaffka <[EMAIL PROTECTED]> writes:
> > We have problems with backend processes that close the channel because of
> > palloc() failures. When an INSERT statement fails, the backend reports an
> > error (e.g. `Cannot insert a duplicate key into a unique index') and
> > allocates a few byte
I'm novice in database world.
Now I have to make design a database where categorized items should be
stored. It resembles the structure something like seen in Yahoo.
Thanks for reading and generous comments of yours.
==
Doo Suk Yang wrote:
>
> I'm novice in database world.
> Now I have to make design a database where categorized items should be
> stored. It resembles the structure something like seen in Yahoo.
>
> Thanks for reading and generous comments of yours.
I do it something like this..
create table cat
