Just for fun I changed the extension of my SPI function and trigger
source file from .c to .C and tried to compile it:
g++ -g -Wall -I /usr/include/postgresql -fPIC -pedantic-c -o bid_control.o
bid_control.C
In file included from /usr/include/postgresql/nodes/relation.h:18,
On Fri, 29 Sep 2000, Bruce Momjian wrote:
Where are we on this?
Create from this non-used residual space chunk and remove it into free
chunk list.
This is really old story. I hope that Tom think of this and has it's
in his care. A problem is that standard day of this planet has
Hi,
The subject says it all.
I want to mess up the backend so...
Do I need lex or flex?
Do I need autoconf (does it even exist for Windows)?
Do I need Cygnus?
Do I need any other aditional packages?
Does it compile with VC6?
Does nmake do or do I need gnu make?
Or is it easier to play around
It recently came to my attention that, when dumping a single table and
using the --blobs option, pg_dump will dump all BLOBs (not just those
referenced by the table). Similarly, restoring a single table from a backup
will restore all the BLOBs.
This is (at least) non-intuitive.
Unfortunately,
Karel Zak [EMAIL PROTECTED] writes:
This is really old story. I hope that Tom think of this and has it's
in his care. A problem is that standard day of this planet has
24 hours for all people (incl. Tom :-), right?
Yup. I've got one more area to wrap up in the new-features business
(I
"Jarmo Paavilainen" [EMAIL PROTECTED] writes:
Or is it easier to play around with the source in Linux?
Yes. You could maybe do it in a Cygwin environment, but I think
it'd be an exercise in frustration.
What do I need in Linux (Cygnus, lex, flex...)?
As long as you install development tools
Stephan Szabo writes:
With that, I do have a general question though. Are referential actions
supposed to be limited by the permissions of the user executing the query?
So, if you for example have write access on the pk table, but not to the
fk table, and there is a on cascade delete
Peter Eisentraut [EMAIL PROTECTED] writes:
The backend process hangs in this loop:
| foreach(temp, rangetable)
Somewhere a list pointer needs to be advanced there.
What? foreach() does advance the pointer. The only way this can be
an infinite loop is if the rangetable list is
Sorry,
Postgres is 6.5.3 on Linux 2.2.10
Ralf
Can I ask about the status of this?
I modified the current ODBC driver for
* referential integrity error reporting,
* SELECT in transactions and
* disabling autocommit.
We are starting to think about organizing additional ODBC testing
Yes, sure. I know that this code (which
Constantin, can you comment on this?
On Wed, 31 May 2000, Bruce Momjian wrote:
I assume this is fixed?
Oh, it is really old letter from me. I total forget...
Hmm, I haven't here last version of CVS, but pgaccess in my comp has this
bug still..
Bruce, thanks for answer.
Tom Lane wrote:
Adriaan Joubert [EMAIL PROTECTED] writes:
we've suddenly started getting this error message out of postgres
(7.0.2). Does anybody know where it comes from?
ERROR: UNLockBuffer: buffer 0 is not locked
Evidently something is passing an invalid buffer number to
12 matches
Mail list logo