Mark Kirkwood wrote:
2) Perhaps leave the trigger + plpgsql function as a plpgsql example,
and refer to it in the (new) data warehouse section/chapter.
Looking at option 2, it seems reasonable to add a trimmed trigger
example into the plpgsql examples section now, and leave the data
warehouse
Attached is a patch that fixes the recently isolated "SMgrRelation
hashtable corrupted" bug by allowing smgrclose() to happen safely
without being called directly by the relcache. The reason this is
an issue is that the relcache might contain a pointer to the
SMgrRelation entry, and if that pointe
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Magnus Hagander wrote:
>> I'm sure it still eneds the shell32 linking.
> I don't see where to put it in the bcc.mak file anyway.
Yeah, I looked in bcc32.mak and didn't see any reference to the other
*32.dll files that win32.mak references. So either B
Magnus Hagander wrote:
The attached patch allows MSCV builds to complete.
Applied.
(I wonder whether the Borland build still works...)
I'm sure it still eneds the shell32 linking. The suorce part should be
the same - AFAIK they ship the MS headers. But I don't have a way to
test it, so
Devrim GUNDUZ wrote:
> http://postgresql.gunduz.org/translation/PostgreSQL-8.0/PgSQL-DilDosy
>alari/postgres-tr.po
> Could you please apply it to -HEAD?
Done.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TI
> > The attached patch allows MSCV builds to complete.
>
> Applied.
>
> (I wonder whether the Borland build still works...)
I'm sure it still eneds the shell32 linking. The suorce part should be
the same - AFAIK they ship the MS headers. But I don't have a way to
test it, so...
> > The warning
