[HACKERS] Hot Standy introduced problem with query cancel behavior

2009-12-26 Thread Kris Jurka
The JDBC driver's regression test suite has revealed a change in behavior introduced by the hot standy patch. Previously when a client sent a cancel request on an idle connection, nothing happened. Now it sends an error message "ERROR: canceling statement due to user request". This confuse

Re: [HACKERS] Hot Standby and cancelling idle queries

2009-12-26 Thread Andres Freund
On Wednesday 25 November 2009 17:25:43 Tom Lane wrote: > Simon Riggs writes: > > An idle-in-transaction transaction can also hold a temporary file. Think > > of an open cursor, for example. Therefore, remove the distinction > > between CONFLICT_MODE_ERROR and CONFLICT_MODE_ERROR_IF_NOT_IDLE, > > i

Re: [HACKERS] Removing pg_migrator limitations

2009-12-26 Thread Bruce Momjian
Bruce Momjian wrote: > Bruce Momjian wrote: > > Tom Lane wrote: > > > Bruce Momjian writes: > > > > Tom Lane wrote: > > > >> The reason I don't want to do it that way is that then you need two > > > >> ugly kluges in the backend, not just one. With the zero-and-add-one > > > >> approach there is

Re: [HACKERS] join ordering via Simulated Annealing

2009-12-26 Thread Andres Freund
On Wednesday 23 December 2009 02:23:55 Jan UrbaƄski wrote: > Hi, > > I've been playing with using a Simulated Annealing-type algorithm for > determinig join ordering for relations. Very cool. > Lastly, I'm lacking good testcases or even a testing approach: I'm > generating silly queries and looki

Re: [HACKERS] Removing pg_migrator limitations

2009-12-26 Thread Bruce Momjian
Bruce Momjian wrote: > Bruce Momjian wrote: > > > Well, we might eventually allow addition of values to enums too; the > > > fact that it's not implemented outside pg_migrator right now doesn't > > > mean we won't ever think of a solution. In any case I'm not persuaded > > > that a zero-element en

[HACKERS] parse_oper cache

2009-12-26 Thread Robert Haas
On Sat, Nov 14, 2009 at 6:36 PM, Tom Lane wrote: > There's an example in parse_oper.c of a specialized cache that's about > as complicated as this would be. I was just taking a look at find_oper_cache_entry() and noticed something odd. When we discover that OprCacheHash == NULL, we make sure tha