Log Message:
---
Update release notes to current CVS.
Modified Files:
--
pgsql/doc/src/sgml:
release.sgml (r1.531 -> r1.532)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/release.sgml?r1=1.531&r2=1.532)
---(end of b
Log Message:
---
Disallow scrolling of FOR UPDATE/FOR SHARE cursors, so as to avoid problems
in corner cases such as re-fetching a just-deleted row. We may be able to
relax this someday, but let's find out how many people really care before
we invest a lot of work in it. Per report from H
Log Message:
---
Remove obsolete statement that you can't update through a cursor.
Modified Files:
--
pgsql/doc/src/sgml/ref:
fetch.sgml (r1.40 -> r1.41)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/fetch.sgml?r1=1.40&r2=1.41)
---
Tom Lane wrote:
> [EMAIL PROTECTED] (Alvaro Herrera) writes:
> > Rearrange vacuum-related bits in PGPROC as a bitmask, to better support
> > having several of them. Add two more flags: whether the process is
> > executing an ANALYZE, and whether a vacuum is for Xid wraparound (which
> > is obvious
[EMAIL PROTECTED] (Alvaro Herrera) writes:
> Rearrange vacuum-related bits in PGPROC as a bitmask, to better support
> having several of them. Add two more flags: whether the process is
> executing an ANALYZE, and whether a vacuum is for Xid wraparound (which
> is obviously only set by autovacuum)
Log Message:
---
Rearrange vacuum-related bits in PGPROC as a bitmask, to better support
having several of them. Add two more flags: whether the process is
executing an ANALYZE, and whether a vacuum is for Xid wraparound (which
is obviously only set by autovacuum).
Sneakily move the worke
Log Message:
---
Fix an error in make_outerjoininfo introduced by my patch of 30-Aug: the code
neglected to test whether an outer join's join-condition actually refers to
the lower outer join it is looking at. (The comment correctly described what
was supposed to happen, but the code didn'
Log Message:
---
Fix an error in make_outerjoininfo introduced by my patch of 30-Aug: the code
neglected to test whether an outer join's join-condition actually refers to
the lower outer join it is looking at. (The comment correctly described what
was supposed to happen, but the code didn'
Log Message:
---
Danish_Danmark -> Danish_Denmark
Modified Files:
--
pgsql/src/bin/initdb:
initdb.c (r1.147 -> r1.148)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/initdb/initdb.c?r1=1.147&r2=1.148)
---(end of broadcast
Log Message:
---
Minor changes to autovacuum worker: change error handling so that it continues
with the next table on schedule instead of exiting, in all cases instead of
just on query cancel.
Add a errcontext() line indicating the activity of the worker to the error
message when it is ca
Hi,
I just updated autovacuum.c with some minor changes and looks like I
managed to involuntarily abort the email to pgsql-committers.
The changeset is here
http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/postmaster/autovacuum.c.diff?r1=1.61;r2=1.62
The commit message was:
Minor ch
Log Message:
---
Fix UPDATE/DELETE WHERE CURRENT OF to support repeated update and update-
then-delete on the current cursor row. The basic fix is that nodeTidscan.c
has to apply heap_get_latest_tid() to the current-scan-TID obtained from the
cursor query; this ensures we get the latest ro
Log Message:
---
Keep heap_page_prune from marking the buffer dirty when it didn't
really change anything. Per report from Itagaki Takahiro. Fix by
Pavan Deolasee.
Modified Files:
--
pgsql/src/backend/access/heap:
pruneheap.c (r1.2 -> r1.3)
(http://develo
Log Message:
---
update french translation.
per Guillaume.
Modified Files:
--
pginst/lang:
fr.xml (r1.26 -> r1.27)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/lang/fr.xml.diff?r1=1.26&r2=1.27)
---(end of broadcas
14 matches
Mail list logo