RE: [HACKERS] vacuum crash on 6.5.3

2000-12-30 Thread Hiroshi Inoue
Just a supplement. Essentially this isn't a crash bug. This had been a disastrous bug that causes data loss silently. (This is known as 'HEAP_MOVED_IN was not expected' bug but the result could be more serious than I've recognized.) Please apply the patch if you still have pre-7.0 pg db-s and yo

[HACKERS] heap_modifytuple() - help needed

2000-12-30 Thread Horst Herb
Can anybodt give me a few examples on how to use heap_modifytuple() efficiently when I do NOT want to modify an attribute through a postgres function? All the examples given in the source seem to use some return of a postgres function (like current user etc). I just want to insert strings into

Re: [HACKERS] GNU readline and BSD license

2000-12-30 Thread Alex Pilosov
On Sat, 30 Dec 2000, Peter Bierman wrote: > At 7:15 PM -0500 12/29/00, Tom Lane wrote: > >Alfred Perlstein <[EMAIL PROTECTED]> writes: > >> Rasmus Lerdorf warned one of you guys that simply linking to GNU > >> readline can contaminate code with the GPL. > > > >> Readline isn't LGPL which permits

[HACKERS] Re: oid failures on Alpha solved

2000-12-30 Thread Brent Verner
On 30 Dec 2000 at 14:24 (-0500), Tom Lane wrote: | > Brent Verner <[EMAIL PROTECTED]> writes: | >> formatting '-1040' with '%u' | >> snprintf = 18446744073709550576 | >> sprintf = 4294966256 | | >> oidout() is where the offending call originates, FWIW. | >> snprintf(result, 12, "%u", o); | | >

Re: [HACKERS] GNU readline and BSD license

2000-12-30 Thread Peter Bierman
At 7:15 PM -0500 12/29/00, Tom Lane wrote: >Alfred Perlstein <[EMAIL PROTECTED]> writes: >> Rasmus Lerdorf warned one of you guys that simply linking to GNU >> readline can contaminate code with the GPL. > >> Readline isn't LGPL which permits linking without lincense issues, >> it is GPL which mea

[HACKERS] Re: [DOCS] Inheritance docs error.

2000-12-30 Thread Tom Lane
Peter Eisentraut <[EMAIL PROTECTED]> writes: They are all correct: UNDER is the new SQL99 syntax, INHERITS is the traditional Postgres syntax. >> >> Current docs do appear to be erroneous: they claim the UNDER phrase goes >> where INHERIT does, which is not what the grammar thinks. I

Re: [HACKERS] GNU readline and BSD license

2000-12-30 Thread Trond Eivind Glomsrød
Lamar Owen <[EMAIL PROTECTED]> writes: > How different is the feature set? Otherwise, sounds like a great idea > to me, and reduces the dependencies substantially -- and makes history > available to all the supported platforms without requiring libreadline > already installed. It bloats on plat

Re: [HACKERS] oid failures on Alpha solved

2000-12-30 Thread Brent Verner
On 30 Dec 2000 at 12:57 (-0500), Tom Lane wrote: | Brent Verner <[EMAIL PROTECTED]> writes: | > formatting '-1040' with '%u' | > snprintf = 18446744073709550576 | > sprintf = 4294966256 | | > oidout() is where the offending call originates, FWIW. | > snprintf(result, 12, "%u", o); | | Hm.

Re: [HACKERS] oid failures on Alpha solved

2000-12-30 Thread Tom Lane
> Brent Verner <[EMAIL PROTECTED]> writes: >> formatting '-1040' with '%u' >> snprintf = 18446744073709550576 >> sprintf = 4294966256 >> oidout() is where the offending call originates, FWIW. >> snprintf(result, 12, "%u", o); > Hm. This is clearly a bug in snprintf. OK, I was able to duplicat

Re: [HACKERS] oid failures on Alpha solved

2000-12-30 Thread Tom Lane
Brent Verner <[EMAIL PROTECTED]> writes: > formatting '-1040' with '%u' > snprintf = 18446744073709550576 > sprintf = 4294966256 > oidout() is where the offending call originates, FWIW. > snprintf(result, 12, "%u", o); Hm. This is clearly a bug in snprintf. Did I understand you correctl

[HACKERS] Just fixed

2000-12-30 Thread Vadim Mikheev
a couple of bugs in new WAL code. Thanks to Tom for pointing to one of them. Initdb is recommended but you can avoid it if shutdown old version properly (format of one of heap log records was changed). Vadim

[HACKERS] Re: GNU readline and BSD license

2000-12-30 Thread mlw
Adam Haberlach wrote: > > On Fri, Dec 29, 2000 at 08:46:40PM -0500, Tom Lane wrote: > > Adam Haberlach <[EMAIL PROTECTED]> writes: > > > RMS already made a big stink about this, claiming that BeOS's use > > > of an emulation layer to link to some GPL'ed network drivers was enough > > > to for

[HACKERS] oid failures on Alpha solved

2000-12-30 Thread Brent Verner
Hi, It turns out the problem causing the oid failures is with our snprintf. specifically we are formatting "%u" incorrectly: using a enhanced-for-testing version of our snprintf I get. formatting '-1040' with '%lu' snprintf = 18446744073709550576 sprintf = 18446744073709550576 formatti

Re: [HACKERS] Creating locales.

2000-12-30 Thread Hannu Krosing
Tim Uckun wrote: > > I have been searching without luck on a howto on how to create locales for > postgres. Could somebody please point me in the general direction? Thanks. > PostgreSQL uses system locales (even to the extent that I was unable to get it use any other locale by setting LC_* var

Re: [HACKERS] Creating locales.

2000-12-30 Thread Oleg Bartunov
You do not need create locale specially for postgres. Postgres uses system locale. You could look at /usr/share/locale regards, Oleg On Wed, 27 Dec 2000, Tim Uckun wrote: > Date: Wed, 27 Dec 2000 10:18:01 -0700 > From: Tim Uckun <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED