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_*
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
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 haven't
looked
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);
|
| Hm. This is
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 linking without
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
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
