Re: [COMMITTERS] pgsql: Repair a low-probability race condition identified by Qingqing

"Tom Lane" <[EMAIL PROTECTED]> wrote > "Qingqing Zhou" <[EMAIL PROTECTED]> writes: > > IMHO the lmgr will not be the murdered by the leftover wakeup, but what > > about the next LockBufferForCleanUp()? > > What about it? It has a loop already. > Oh, right. Regards, Qingqing -

Re: [COMMITTERS] pgsql: Repair a low-probability race condition identified by Qingqing

"Qingqing Zhou" <[EMAIL PROTECTED]> writes: > IMHO the lmgr will not be the murdered by the leftover wakeup, but what > about the next LockBufferForCleanUp()? What about it? It has a loop already. regards, tom lane ---(end of broadcast)---

Re: [COMMITTERS] pgsql: Repair a low-probability race condition identified by Qingqing

"Tom Lane" <[EMAIL PROTECTED]> wrote > Rather than try to prevent the race condition directly, it seems best > to make the lock manager robust against leftover wakeups, by having it > repeat waiting on the semaphore if the lock has not actually been granted > or denied yet. > IMHO the lmgr will n

[COMMITTERS] pgsql: Document that errors are not output by log_statement (was they

Log Message: --- Document that errors are not output by log_statement (was they were in 8.0), and add as suggestion to use log_min_error_statement for this purpose. I also fixed the code so the first EXECUTE has it's prepare, rather than the last which is what was in the current code. Als

[COMMITTERS] pgsql: Document that errors are not output by log_statement (was they

Log Message: --- Document that errors are not output by log_statement (was they were in 8.0), and add as suggestion to use log_min_error_statement for this purpose. I also fixed the code so the first EXECUTE has it's prepare, rather than the last which is what was in the current code. Als

[COMMITTERS] bizgres - bizgres: Added DynamicTransform, which dynamically generates a

Log Message: --- Added DynamicTransform, which dynamically generates a java class to perform any transformation supported by java. Modified Files: -- bizgres/KETL/src/com/kni/etl/ketl: ETLPort.java (r1.4 -> r1.5) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cg

[COMMITTERS] pgpitrha - pgpitrha: Using a more precise regex to determine which files

Log Message: --- Using a more precise regex to determine which files in the pg_xlog directory are actually xlogs at Tom Lane's suggestion. Modified Files: -- pgpitrha/bin: rsynclastlog.sh (r1.1 -> r1.2) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgpitrha

[COMMITTERS] pgfouine - pgfouine: added tooltip with hourly statistics on errors

Log Message: --- added tooltip with hourly statistics on errors report too Modified Files: -- pgfouine/include/reporting/reports: NormalizedErrorsMostFrequentReport.class.php (r1.7 -> r1.8) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pgfouine/pgfouine/incl

[COMMITTERS] bizgres - bizgres:

Log Message: --- Modified Files: -- bizgres/KETL/src/com/kni/etl: SQLJob.java (r1.3 -> r1.4) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/bizgres/bizgres/KETL/src/com/kni/etl/SQLJob.java.diff?r1=1.3&r2=1.4) ---(end of broadcast)---

[COMMITTERS] pgsql: Fix the torn-page hazard for PITR base backups by forcing full

Log Message: --- Fix the torn-page hazard for PITR base backups by forcing full page writes to occur between pg_start_backup() and pg_stop_backup(), even if the GUC setting full_page_writes is OFF. Per discussion, doing this in combination with the already-existing checkpoint during pg_sta

[COMMITTERS] oledb - oledb: Prepare version 1.0.0.20

Log Message: --- Prepare version 1.0.0.20 Modified Files: -- oledb: ChangeLog (r1.17 -> r1.18) (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/oledb/oledb/ChangeLog.diff?r1=1.17&r2=1.18) OleDb.rc (r1.21 -> r1.22) (http://cvs.pgfoundry.org/cgi-