Re: [PATCHES] plpgpsm

2007-05-01 Thread Pavel Stehule
Hello, I actualised sql/psm patch: added: * last Tom's plpgsql patches (some fixes and enum support) * scrollable cursor's support new version is on http://www.pgsql.cz/patches/plpgpsm0501.diff.gz Regard Pavel Stehule Your patch has been added to the PostgreSQL unapplied patches list at:

[PATCHES] MSVC installation wrapper script

2007-05-01 Thread Dave Page
Per previous discussion with Magnus, the attached batch file (rename to install.bat) is a wrapper script for the MSVC installer. It sets up the environment before installing (to allow zic.exe to run properly), and removes the need to explicitly call perl on the command line. This should be

Re: [PATCHES] MSVC installation wrapper script

2007-05-01 Thread Magnus Hagander
Dave Page wrote: Per previous discussion with Magnus, the attached batch file (rename to install.bat) is a wrapper script for the MSVC installer. It sets up the environment before installing (to allow zic.exe to run properly), and removes the need to explicitly call perl on the command line.

Re: [PATCHES] [HACKERS] autovacuum does not start in HEAD

2007-05-01 Thread Alvaro Herrera
ITAGAKI Takahiro wrote: I wrote: I found that autovacuum launcher does not launch any workers in HEAD. The attached autovacuum-fix.patch could fix the problem. I changed to use 'greater or equal' instead of 'greater' at the decision of next autovacuum target. I developed a different fix,

Re: [PATCHES] [GENERAL] dropping role w/dependent objects

2007-05-01 Thread Tom Lane
Ed L. [EMAIL PROTECTED] writes: [ enlarge MAX_REPORTED_DEPS to 2000 ] I was about to apply this, but stopped to reflect that it is probably not such a hot idea. My concern is that enormously long error message detail fields are likely to break client software, particularly GUI clients. A poor

Re: [PATCHES] [GENERAL] dropping role w/dependent objects

2007-05-01 Thread Ed L.
On Tuesday 01 May 2007 9:34 pm, Tom Lane wrote: Ed L. [EMAIL PROTECTED] writes: [ enlarge MAX_REPORTED_DEPS to 2000 ] I was about to apply this, but stopped to reflect that it is probably not such a hot idea. My concern is that enormously long error message detail fields are likely to