I recently upgraded my DB from 7.4.3 to 8.0.4 and I've noticed the following errors appearing in my serverlog:
2005-11-03 05:56:57 CST 127.0.0.1(38858) ERROR: Unicode characters greater than or equal to 0x1 are not supported
2005-11-03 06:04:09 CST 127.0.0.1(38954) ERROR: invalid byte s
d
the DB. I've done this on my Linux server many times and it never
complained. I won't be doing that again.
-Don
On Apr 11, 2005 1:29 AM, Tom Lane <[EMAIL PROTECTED]> wrote:
> Don Drake <[EMAIL PROTECTED]> writes:
> > My server is crashing on a delete statement.
My server is crashing on a delete statement.
Here's the error message in the log file:
LOCATION: ShutdownXLOG, xlog.c:3090
LOG: 0: database system is shut down
LOCATION: ShutdownXLOG, xlog.c:3104
LOG: 0: database system was shut down at 2005-04-10 21:54:34 CDT
LOCATION: StartupXLOG,
On Tue, 25 Jan 2005 11:18:05 -0500, Tom Lane <[EMAIL PROTECTED]> wrote:
> Don Drake <[EMAIL PROTECTED]> writes:
> > This morning I found the postgres not running and the following in my log
> > file:
>
> > 2005-01-25 01:38:22 FATAL: could not create shared
My db server is running under high load recently and the number of
connections during the morning hours is actually very high.
This morning I found the postgres not running and the following in my log file:
DETAIL: The postmaster has commanded this server process to roll back
the current transac
I've read the previous thread on the list regarding partitioning
mechanisms and I just wrote a plpgsql function to create the partition
tables (by date) as well as another function used to do the insert (it
determines which table will be inserted).
The creation of the partition tables uses the inh
