|
|
 Up |
|
|
  |
Author: Simon RiggsSimon Riggs
Date: Sep 5, 2008 08:14
http://developer.postgresql.org/pgdocs/postgres/functions-info.html
xip_list is described as
"Active txids at the time of the snapshot... "
This is incorrect. The xip_list is the list of transactions that are in
progress *and* less than xmax. There may be transactions in progress
with an xid higher than xmax. This will happen frequently in fact. This
is because xmax is defined as the highest/latest completed xid, not the
highest running xid.
Note that there is no way to discover the list of running xids at the
time of the snapshot, from the data we hold about snapshots. Nor can the
snapshot data be used to monitor the number of transactions in progress.
Anyone disagree? If not, I'll patch.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
|
| |
|
| |
1 Comment |
|
|
Author: Bruce MomjianBruce Momjian
Date: Aug 15, 2008 17:22
Peter Eisentraut wrote:
> I tried building TODO.html from TODO according to the description in
> doc/src/FAQ/README, but saw the following kind of difference repeating:
>
> @@ -24,7 +24,7 @@
>
>
>
> - - -Allow administrators to safely terminate individual sessions either
> + - -Allow administrators to safely terminate individual sessions either
> via an SQL function or SIGTERM
> - Check for unreferenced table files created by transactions that were
> in-progress when the server terminated abruptly
>
> Apparently, there is a piece of code missing that adds these tags around
> the done items. Bruce, do you have this code, and can you add it to the README?
These two lines in pgsql/src/tools/TODO2html should be adding "*"s which
is then interpreted as "":
|
| Show full article (1.34Kb) |
|
| |
no comments
|
|
|
|
|
|
Author: MoralesMorales
Date: Aug 4, 2008 09:12
=======================================
Why PAY TOO MUCH for FUEL
Learn how to protect our
Environment and Reduce unnecessary
spending
=======================================
http://www.fuellegacy.com/dkokeefe
=======================================
@ldui
|
| |
|
no comments
|
|
|
Author: WestlandbtWestlandbt
Date: May 24, 2008 21:04
WereEveryWhere.net seeks to become the most popular Social Networking Website
offering an interactive, user-submitted network of friends, personal profiles,
video chat, blogs, groups, photos, music and videos for adults internationally.
Log on at http://www.WereEveryWhere.net Its FREE!
-----------------------------------------------------------------------------
--This Message Has Been Posted Using A Trial Version Of Message Poster 2003--
-----------------------------------------------------------------------------
Would you like to reach millions of customers for only the cost of bandwidth?
You can post messages like this to thousands of newsgroups with a simple to
use software application called Message Poster 2003. For more details on
this extremely affordable software, visit:
http://www.exibitionsoftware.com
|
| |
|
no comments
|
|
|
Author: Tom LaneTom Lane
Date: May 17, 2008 09:55
"Jaime Casanova" gmail.com> writes:> But in my freshly 8.3.1 instalation on win xp, the default is
> "fsync"... is a *bug* in the docs :)
More like a bug in the code. Does it let you set the value to
open_datasync?
regards, tom lane
|
| |
|
no comments
|
|
|
Author: monaleebmonaleeb
Date: May 17, 2008 01:18
Dear,
If anybody having rpm for Suse 10.2 for 64 bit plz send me.
And also help me to start the server?
MOnalee Bhandge.
Database Administrator.
Sungrace Infotech.
Nashik.
|
| |
|
no comments
|
|
|
Author: Simon RiggsSimon Riggs
Date: May 9, 2008 07:49
On Fri, 2008-05-09 at 10:35 -0400, Bruce Momjian wrote:
> The comment is saying "the second part of the file name" can be ignored,
> not the backup file itself.
Yes, I know. I'm asking if anyone minds me changing the docs to make it
clearer, not being confused by it myself. The issue was raised because
pg_standby doesn't treat the file as optional, though recovery code
does.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
|
| |
|
no comments
|
|
|
Author: Simon RiggsSimon Riggs
Date: May 9, 2008 07:43
On Fri, 2008-05-09 at 10:28 -0400, Tom Lane wrote:
> Simon Riggs 2ndquadrant.com> writes:>> Just had questions from a replication user about why the .backup file is
>> described as "can ordinarily be ignored" and is considered optional by
>> recovery also even when pg_start_backup() was used.
>
> What it says is that the second part of the filename can ordinarily
> be ignored. I don't know why neither he nor you managed to parse the
> sentence correctly. Feel free to propose a rewording, but removing
> information doesn't sound like a solution.
Its probably best to read the whole mail before commenting on other
people's parsing. ;-)
I'll do a patch.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
|
| Show full article (0.89Kb) |
|
no comments
|
|
|
|
|
|
Author: Bruce MomjianBruce Momjian
Date: May 9, 2008 07:37
Simon Riggs wrote:
> Just had questions from a replication user about why the .backup file is
> described as "can ordinarily be ignored" and is considered optional by
> recovery also even when pg_start_backup() was used.
>
> If the file was created, it is necessary to use it in recovery, so
> should never be ignored as the docs imply.
>
> Can we remove the phrase ", and can ordinarily be ignored." ? from
> doc/src/sgml/backup.sgml
>
>
> To make use of the backup, you will need to keep around all the WAL
> segment files generated during and after the file system backup.
> To aid you in doing this, the pg_stop_backup function
> creates a backup history file that is immediately
> stored into the WAL archive area. This file is named after the first
> WAL segment file that you need to have to make use of the backup.
> For example, if the starting WAL file is
> 0000000100001234000055CD the backup history file will be ...
|
| Show full article (2.10Kb) |
|
no comments
|
|
|
|
|
|
|
