Update of /cvsroot/pgsql/contrib/txid
In directory cvs.postgresql.org:/tmp/cvs-serv49696/txid
Log Message:
Directory /cvsroot/pgsql/contrib/txid added to the repository
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore
Update of /cvsroot/pgsql/contrib/txid/sql
In directory cvs.postgresql.org:/tmp/cvs-serv50020/sql
Log Message:
Directory /cvsroot/pgsql/contrib/txid/sql added to the repository
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Update of /cvsroot/pgsql/contrib/txid/expected
In directory cvs.postgresql.org:/tmp/cvs-serv50020/expected
Log Message:
Directory /cvsroot/pgsql/contrib/txid/expected added to the repository
---(end of broadcast)---
TIP 5: don't forget to increase
Log Message:
---
Added the Skytools extended transaction ID module to contrib as discussed
on CORE previously.
This module offers transaction ID's containing the original XID and the
transaction epoch as a bigint value to the user level. It also provides
a special txid_snapshot data type
On 9/15/2007 10:37 PM, Tom Lane wrote:
Log Message:
---
Fix aboriginal mistake in lazy VACUUM's code for truncating away
no-longer-needed pages at the end of a table. We thought we could throw away
pages containing HEAPTUPLE_DEAD tuples; but this is not so, because such
tuples very
On 9/5/2007 2:10 PM, Tom Lane wrote:
Log Message:
---
Implement lazy XID allocation: transactions that do not modify any database
rows will normally never obtain an XID at all. We already did things this way
As a side note, this patch is transparent enough that it doesn't seem to
Log Message:
---
Added a new scripting meta command
\usleep [milliseconds|:variable]
which can be used in -f scripts to insert a thinking time between
other commands.
Jan
Modified Files:
--
pgsql/contrib/pgbench:
README.pgbench (r1.18 - r1.19)
Log Message:
---
Changed new \usleep command into \sleep with an optional time unit
argument to specify us, ms or s. As per suggestion by Peter E.
Jan
Modified Files:
--
pgsql/contrib/pgbench:
README.pgbench (r1.19 - r1.20)
Log Message:
---
The session_replication_role actually can be changed at will during
a session regardless of the existence of cached plans. The plancache
only needs to be invalidated so that rules affected by the new setting
will be reflected in the new query plans.
Jan
Modified Files:
Log Message:
---
Changes pg_trigger and extend pg_rewrite in order to allow triggers and
rules to be defined with different, per session controllable, behaviors
for replication purposes.
This will allow replication systems like Slony-I and, as has been stated
on pgsql-hackers, other
Log Message:
---
Bumping catversion due to changes to pg_trigger and pg_rewrite.
BTW, the comment in this file says that we hope we never have more than
10 catversion changes per day, but to even make this possible we should
start counting at zero, shouldn't we?
Jan
Modified Files:
On 3/20/2007 12:00 AM, Neil Conway wrote:
Jan Wieck wrote:
BTW, the comment in this file says that we hope we never have more than
10 catversion changes per day, but to even make this possible we should
start counting at zero, shouldn't we?
The comment says hopefully we'll never commit ten
On 3/20/2007 12:08 AM, Jan Wieck wrote:
On 3/20/2007 12:00 AM, Neil Conway wrote:
Jan Wieck wrote:
BTW, the comment in this file says that we hope we never have more than
10 catversion changes per day, but to even make this possible we should
start counting at zero, shouldn't we
On 12/2/2004 5:28 PM, Bruce Momjian wrote:
Log Message:
---
On win32, there is currently no way to get the equivalent function of
the ps argument list on Unix - meaning that there is no way to
identify for example the stats processors or the bgwriter.
doesn't tlist.exe work for that?
Jan
On 12/3/2004 10:36 AM, Dave Page wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jan Wieck
Sent: 03 December 2004 15:04
To: Bruce Momjian
Cc: [EMAIL PROTECTED]
Subject: Re: [COMMITTERS] pgsql: On win32, there is currently
no way to get
On 12/2
On 8/7/2004 12:47 AM, Tom Lane wrote:
[EMAIL PROTECTED] (Jan Wieck) writes:
Vacuum delay activated by default.
What? If there was consensus to do this, I missed it. If there was
even any *discussion* of doing this, I missed it.
regards, tom lane
How many questions about vacuum still grabbing
On 8/7/2004 2:06 PM, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Just curious, but isn't this one of the key points about pg_autovacuum in
the first place? So that you vacuum what needs to be vacuum'd, and not
*everything* ... ? Shouldn't the answer to the 'bandwidth issue'
Log Message:
---
Vacuum delay activated by default.
Jan
Modified Files:
--
pgsql-server/src/backend/utils/misc:
guc.c (r1.227 - r1.228)
(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/backend/utils/misc/guc.c.diff?r1=1.227r2=1.228)
Tom Lane wrote:
[EMAIL PROTECTED] (Bruce Momjian) writes:
someone asked me about the FK deadlock fix, mentioned in the 7.3.3
release notes as 3rd change:
http://www.postgresql.org/docs/current/static/release-7-3-3.html
Actually, that fix was available with 7.4, not
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/02/11 21:44:22
Modified files:
src/backend/utils/adt: pgstatfuncs.c
Log message:
Added hints about the reason, why the command string in
the view pg_stat_activity is missing,
Log Message:
---
Please apply this minor patch to the cvs HEAD of dbmirror
It fixes a typo in a define
Thanks
-- Steven Singer
Modified Files:
--
pgsql-server/contrib/dbmirror:
pending.c (r1.17 - r1.18)
Fabien COELHO wrote:
OK, patch reverted at request of Tom and Peter. Please propose a more
generalitzed soluion. Thanks.
Sigh.
You refuse a 10 lines patch to access a stupid opaque type in the backend.
You both refuse some things to be done in the back end, and also to add
what is needed to do
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/02/13 08:25:10
Modified files:
doc/src/sgml : runtime.sgml
Log message:
Documentation for vacuum_cost config options.
Jan
---(end of
Bruce Momjian wrote:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/02/12 13:31:09
Modified files:
doc: TODO
Log message:
Not needed:
* Add MATCH PARTIAL referential integrity [foreign]
* Add MATCH
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/02/12 11:06:56
Modified files:
src/backend/storage/buffer: buf_init.c bufmgr.c freelist.c
src/include/storage: buf_internals.h
Log message:
Fixed bug where
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/02/06 15:36:18
Modified files:
src/backend/access/nbtree: nbtree.c
src/backend/commands: vacuumlazy.c
src/backend/storage/buffer: bufmgr.c freelist.c
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/02/03 21:24:54
Modified files:
src/backend/storage/buffer: bufmgr.c
src/backend/utils/misc: guc.c postgresql.conf.sample
src/include/storage: bufmgr.h
Log message:
Tom Lane wrote:
Jan Wieck [EMAIL PROTECTED] writes:
The whole point of the bgwriter is to give responsetimes a better
variance, I never claimed that it will improve performance.
I want to use it to improve reliability, by getting rid of our
dependence on sync(). The bgwriter can afford to wait
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 04/01/15 12:14:26
Modified files:
src/backend/storage/buffer: buf_init.c freelist.c
src/include/storage: buf_internals.h
Log message:
Adjusted calculation of shared memory
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/11/16 12:41:01
Modified files:
src/backend/storage/buffer: freelist.c
src/backend/utils/misc: guc.c postgresql.conf.sample
Log message:
Changed parameter name for shared
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/11/14 00:32:11
Modified files:
src/backend/storage/buffer: README
Log message:
Added documentation for the new interface between the buffer manager
and the cache replacement
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/11/12 20:40:02
Modified files:
src/backend/commands: vacuum.c
src/backend/storage/buffer: buf_init.c buf_table.c bufmgr.c
freelist.c
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/30 23:58:21
Modified files:
src/backend/utils/adt: ri_triggers.c
src/test/regress/expected: foreign_key.out
src/test/regress/sql: foreign_key.sql
Log message:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/31 10:27:57
Modified files:
src/test/regress/expected: foreign_key.out rules.out
src/test/regress/sql: foreign_key.sql rules.sql
Log message:
Moved the recently added
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/30 23:57:42
Modified files:
src/backend/utils/adt: Tag: REL7_3_STABLE ri_triggers.c
src/test/regress/expected: Tag: REL7_3_STABLE foreign_key.out
src/test/regress/sql:
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/31 10:27:51
Modified files:
src/test/regress/expected: Tag: REL7_3_STABLE foreign_key.out
rules.out
src/test/regress/sql: Tag: REL7_3_STABLE
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/29 22:00:44
Modified files:
src/pl/tcl : Tag: REL7_3_STABLE pltcl.c
Log message:
Support for qualified type names in PL/Tcl's spi_prepare command.
This is not
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/10/08 22:17:07
Modified files:
src/interfaces/jdbc/org/postgresql/jdbc1:
AbstractJdbc1Statement.java
Log message:
Protected access
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/09/29 16:24:06
Modified files:
src/pl/tcl : pltcl.c
Log message:
Fixed type lookup in spi_prepare for possible qualified
type name specification.
Jan
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/09/28 14:46:19
Modified files:
src/bin/pg_dump: Tag: REL7_3_STABLE pg_dump.c
Log message:
Backpatched changes for rules when casts are dumped according to
discussion on
CVSROOT:/cvsroot
Module name:pgsql-server
Changes by: [EMAIL PROTECTED] 03/09/27 12:34:06
Modified files:
src/bin/pg_dump: pg_dump.c
Log message:
Changed the logic when a CAST is dumped according to discussion
on pgsql-hackers.
A
41 matches
Mail list logo
