these errors *should* be fixed ... we had problems with the database
server this morning, but we think we've exorcised the demons ...
On Fri, 13 Jul 2001 [EMAIL PROTECTED] wrote:
> Jill Gemmill ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
long ago gone ... if you want to get on a list to post to, without being
swamped with email, send a 'subscribe-nomail' to the -request address for
the list ... especially great for those using news to post to the lists :)
On Wed, 17 Jan 2001, Jason Schroeder wrote:
> http://www.postgresql.org/
He's just gone through a very painful move of his domain, where his old
provider "wouldn't let go" ... I talked to him the other day and he's just
getting settled back in again as far as email and all that is concerned
...
On Tue, 16 Jan 2001, Stanislas Pinte wrote:
>
> I confirm the bug, we ex
On Thu, 2 Nov 2000 [EMAIL PROTECTED] wrote:
> P. Ashok Kumar ([EMAIL PROTECTED]) reports a bug with a severity of 2
> The lower the number the more severe it is.
>
> Short Description
> performace about your search engine
>
> Long Description
> You search engine takes long time to give results
fixed, thanks ...
On Tue, 31 Oct 2000, Evelyn Mitchell wrote:
> - Forwarded message from Mail Delivery Subsystem
><[EMAIL PROTECTED]> -
>
> Date: Tue, 31 Oct 2000 12:50:35 -0500 (EST)
> From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Subject: Returned ma
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: [EMAIL PROTECTED] secondary: scrappy@{freebsd|postgresql}.org
the only way of initializing it (to the best of my knowledge) is to backup
your databases (pg_dump) and a re-initdb of the database ... one person
recently rm'd the pg_log and found out just how disasterous that is :(
btw, would heavily recomment upgrading to 7.0.2 while you are at it, which
has
On Sun, 22 Oct 2000, Bruce Momjian wrote:
> > Palle Girgensohn <[EMAIL PROTECTED]> writes:
> > > GNU gdb 4.18
> > > Program terminated with signal 11, Segmentation fault.
> > > (gdb) bt
> > > #0 0x8136eb2 in GetTemplateEncoding ()
> > > #1 0x8136d66 in pg_mb2wchar_with_len ()
> > > #2 0x8
try 'vacuum verbose;' ... if that doesn't work, try doing a pg_dump/reload
... and, above all ... upgrade to v7.x as soon as possible ...
On Tue, 29 Aug 2000, Ange Michel POZZO wrote:
> hi all,
>
> i use [PostgreSQL 6.5.2 on i686-pc-linux-gnu, compiled by gcc 2.95.2] on a
> linux mandrake 7.0
appears to work much better now ... :)
On Thu, 24 Aug 2000 [EMAIL PROTECTED] wrote:
> Vince ([EMAIL PROTECTED]) reports a bug with a severity of 4
> The lower the number the more severe it is.
>
> Short Description
> testing the reply to
>
> Long Description
> Check out the reply-to (it shou
Okay, my first question is is *what* OS are you running on? I get this
sort of error under Solaris if I use a defautl install of both the OS and
PostgreSQL, and have to use the -B option to reduce the number of segments
that PostgreSQL wants to configure ...
v6.5.3, I believe it was, changed th
11 matches
Mail list logo
