* Tom Lane ([EMAIL PROTECTED]) [030214 19:35]:
Lance Thomas [EMAIL PROTECTED] writes:
Below is something that may be of interest -- a short, 7-statement script
that seems to drop my postgres server.
It appears that the plpython trigger implementation assumes that any
given procedure will
In a plpython trigger, if you return MODIFY, the parsing of the
TD[new] dictionary uses the wrong (c array) index to locate the
atttypmod value, leading to subtle bugs dependent on the exact types,
names, and order of fields in the table in question.
(Types need to be those that use the typmod,
* mlw ([EMAIL PROTECTED]) [020424 18:51]:
(2) Use programmatic hints which allow coders specify which indexes are used
during a query. (ala Oracle)
We would certainly use this if it were available. Hopefully not to
shoot ourselves in the foot, but for the rather common case of having
a
* Bruce Momjian ([EMAIL PROTECTED]) [020423 12:30]:
1 - All SETs are rolled back in aborted transaction
2 - SETs are ignored after transaction abort
3 - All SETs are honored in aborted transaction
? - Have SETs vary in behavior depending on variable
Our
Patch against 7,2 submitted for comment.
It's a little messy; I had some trouble trying to reconcile the code
style of libpq which I copied from, and odbc.
Suggestions on what parts look ugly, and or where to send this
(is there a separate ODBC place?) are welcome.
This seems to work just
* Tom Lane ([EMAIL PROTECTED]) [020402 16:42]:
Since I'm about to have to edit pg_proc.h to add a namespace column,
I thought this would be a good time to revise the current proiscachable
column into the three-way cachability distinction we've discussed
before. But I need some names for the
Original titles:
Patch to add real cancel to ODBC driver
Patch to add real can--cel to ODBC driver
Bruce, sorry to bother you, would you forward this onto the list?
I can't post for reasons I can't fathom.
-
Patch against 7,2 submitted for comment.
It's a little messy; I had some
Patch against 7,2 submitted for comment.
It's a little messy; I had some trouble trying to reconcile the code
style of libpq which I copied from, and odbc.
Suggestions on what parts look ugly, and or where to send this
(is there a separate ODBC place?) are welcome.
This seems to work just
, or is there an existing
standard for factoring the body of the int8in function into a
widely available utility location.
Hope those questions are clear. I'd like to get a patch in
before Beta.
-Brad
* Bradley McLean ([EMAIL PROTECTED]) [010929 01:55]:
Can someone else run this and confirm the results
* Gavin Sherry ([EMAIL PROTECTED]) [010930 06:13]:
On Sat, 29 Sep 2001 [EMAIL PROTECTED] wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
How hard would it be to pre-fork an extra backend
How are you going to pass the connection socket to an already-forked
child process? AFAIK
Can someone else run this and confirm the results against the tip
of the CVS repository?
I'm trying to trace this bug (help welcome too).
(it was hidden in a trigger and a pain to narrow to this point)
-Brad
-
drop function mul1(int4,int4);
drop function mul2(int4,int4);
drop function
11 matches
Mail list logo