not be able to make implications from that.
I'll think on this some more, but not for 8.2.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire
, current approach I am taking is better than that.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
statement_cost_* in many
places sounds useful to me and not too hard to get into 8.2
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Sun, 2006-07-16 at 10:51 -0400, Tom Lane wrote:
Andreas Seltenreich [EMAIL PROTECTED] writes:
Simon Riggs [EMAIL PROTECTED] writes:
[2. text/x-patch; restartableRecovery.patch]
Hmm, wouldn't you have to reboot the resource managers at each
checkpoint? I'm afraid otherwise things like
to ensure their atomicity.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Sun, 2006-07-16 at 15:33 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Sun, 2006-07-16 at 12:40 -0400, Tom Lane wrote:
A compromise that might be good enough is to add an rmgr routine defined
as bool is_idle(void) that tests whether the rmgr has any open state
of a
couple months ago). However, downside #3 might be a stronger objection
for lmgr, since it can create or destroy lock objects without necessarily
doing any I/O.
We should be in a position to test this soon.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
be doubles.
Makes no sense to me as a real. It should be an integer, since it is the
effective number of cache pages, not KB, MB or GB.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have
(integer) = max # secs between log file switches
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
() will only make things more complicated
and less flexible.
Putting it into pg_stop_backup was what we previously agreed.
Where is the loss of flexibility?
I need to get this straight because I was actually intending to do this
for 8.2, i.e. next few days.
--
Simon Riggs
be contingent on
some future event.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Tue, 2006-07-25 at 11:53 -0400, Tom Lane wrote:
That's fine, but feature freeze is in a week and we don't even have
the
basic function for manually doing a log file switch. Let's get that
done first and then think about automatic switches.
Agreed.
--
Simon Riggs
()
pg_stop_backup(boolean); --parameter says log switch or not
Most people use the existing parameter-less function,
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0
On Tue, 2006-07-25 at 11:57 -0400, Bruce Momjian wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I was planning to add a new GUC
archive_timeout (integer) = max # secs between log file switches
That's fine, but feature freeze is in a week and we don't even have
it happen.
Comments? For the existing AMs this is a pretty trivial change, and
I'd be willing to commit to making it happen before feature freeze if
it seems useful.
Bitmap indexes are worth having, but they must be well integrated.
This sounds like the way to go.
--
Simon Riggs
case and it will be just
confusing for people.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Sun, 2006-07-16 at 01:04 +0300, Hannu Krosing wrote:
Ühel kenal päeval, R, 2006-07-14 kell 17:39, kirjutas Simon Riggs:
On Fri, 2006-07-14 at 12:09 -0400, Tom Lane wrote:
Florian G. Pflug [EMAIL PROTECTED] writes:
I've now thought about how to fix that without doing that rather
crude
On Tue, 2006-08-01 at 00:40 +0300, Hannu Krosing wrote:
Ühel kenal päeval, T, 2006-07-25 kell 17:05, kirjutas Simon Riggs:
On Tue, 2006-07-25 at 11:53 -0400, Tom Lane wrote:
That's fine, but feature freeze is in a week and we don't even have
the
basic function for manually doing a log
On Tue, 2006-08-01 at 00:40 +0300, Hannu Krosing wrote:
Ühel kenal päeval, T, 2006-07-25 kell 17:05, kirjutas Simon Riggs:
On Tue, 2006-07-25 at 11:53 -0400, Tom Lane wrote:
That's fine, but feature freeze is in a week and we don't even have
the
basic function for manually doing a log
the panel think? Take the red pill, or stick with blue?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan
it isn't going to hit the main feature freeze?
I'll be able to spend more time with him on that now.
Do we care whether that's part of the release or not? It's a pretty
specific tool.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end
On Sun, 2006-07-16 at 20:56 +0100, Simon Riggs wrote:
On Sun, 2006-07-16 at 15:33 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Sun, 2006-07-16 at 12:40 -0400, Tom Lane wrote:
A compromise that might be good enough is to add an rmgr routine defined
as bool is_idle
an outstanding question on how to include LWlock support into
the archiver, required to flesh out the feature set, and of course
assuming these patches being accepted.]
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
On Wed, 2006-08-02 at 18:49 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
[I have an outstanding question on how to include LWlock support into
the archiver, required to flesh out the feature set, and of course
assuming these patches being accepted.]
The archiver
On Thu, 2006-08-03 at 13:38 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
WIP archive_timeout.
All we need to do is add LWLock support to archiver.
Thoughts/ideas/hints welcome.
Hint: this isn't the archiver's problem, and so you don't need to get
the archiver involved
On Thu, 2006-08-03 at 18:00 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Patch included to implement xlog switching, using an xlog record
processing instruction and forcibly moving xlog pointers.
Just to be clear --- does this fully supersede your draft patch of
27-July
On Thu, 2006-08-03 at 19:03 +0100, Simon Riggs wrote:
On Thu, 2006-08-03 at 13:38 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
WIP archive_timeout.
All we need to do is add LWLock support to archiver.
Thoughts/ideas/hints welcome.
Hint: this isn't the archiver's
.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
scripts that do get it right. Instead, we can put
the boundary-case logic into the new functions that extract a filename
from the WAL location string that the action functions return.
This is done right? Ping me back if there's anything more to add.
--
Simon Riggs
EnterpriseDB http
of that in mind, I think renaming the current GUC would be a
fairly short-lived name change, so I'd suggest sticking with it until
the functions have been enhanced to the point we can dream up a slightly
more evocative name.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
On Mon, 2006-08-07 at 11:37 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
If we are in standby mode, then rather than ending recovery we go into a
wait loop. We poll for the next file, then sleep for 1000 ms, then poll
again. When a file arrives we mark a restartpoint each
On Mon, 2006-08-07 at 13:05 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I've implemented this for BTree, GIN, GIST using an additional rmgr
functionbool rm_safe_restartpoint(void)
...
Recovery checkpoints are now renamed restartpoints to avoid
confusion
file. Having it be the Insert pointer
could lead to some errors.
Any objections if I correct that?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map
/care what a
postmaster or a backend is and what implications those phrases carry.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Wed, 2006-08-09 at 10:04 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Something Hannu wrote has just reminded me that
pg_current_xlog_location() returns the current Insert pointer rather
than the current Write pointer.
That would not be useful for streaming xlog records
pointer i.e. the offset up
to which you can read() the xlog file and trust what it tells you
pg_current_wal_insert_pointer() - gives the insert pointer :-)
Named sufficiently differently that there is no confusion between them.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
On Sun, 2006-08-13 at 22:50 -0400, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
This issue is closed, right?
We've agreed we need two functions, but it's not done yet. Seems pretty
trivial though ...
Just back from India. I'll work on this tonight.
--
Simon Riggs
On Fri, 2006-08-11 at 08:04 +0100, Simon Riggs wrote:
On Thu, 2006-08-10 at 08:57 -0400, Tom Lane wrote:
Anyway, after further thought I've concluded that we really should
supply something that returns the Insert pointer, as this would be
useful for debugging and system-monitoring
On Tue, 2006-08-15 at 11:10 -0400, Alvaro Herrera wrote:
Simon Riggs wrote:
postgres=# select pg_xlogfile_name_offset(pg_switch_xlog());
pg_xlogfile_name_offset
---
00010001 16777216
(1 row)
I've not taken up Jim Nasby's
On Tue, 2006-08-15 at 12:13 -0500, Jim C. Nasby wrote:
On Tue, Aug 15, 2006 at 06:07:12PM +0100, Simon Riggs wrote:
On Tue, 2006-08-15 at 11:10 -0400, Alvaro Herrera wrote:
Simon Riggs wrote:
postgres=# select pg_xlogfile_name_offset(pg_switch_xlog
be greatly appreciated.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Wed, 2006-08-16 at 08:51 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2006-08-15 at 18:42 -0400, Tom Lane wrote:
So let's fix pg_xlogfile_name_offset() to have two OUT parameters
instead of returning a smushed-together string.
I'll do this, but I'm conscious
On Wed, 2006-08-16 at 11:45 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
We want a single row output, with two columns, yes?
Presumably:
xlogfilenameTEXT
offset INTEGER
Sounds right to me. int4 should be wide enough for practical xlog
segment
On Wed, 2006-08-16 at 16:51 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
but my initdb fails with
creating template1 database in a/base/1 ... FATAL: cache lookup failed
for type 26
Um ... when did you last cvs update? That was the behavior up till I
fixed array_in
On Wed, 2006-08-16 at 17:09 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Wise one: what should my pg_proc look like?
DATA(insert OID = 2850 ( pg_xlogfile_name_offsetPGNSP PGUID 12 f f t f
i 1 2249 25 25 25 23 i o o _null_ pg_xlogfile_name_offset -
_null_ ));
Oh
it.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Thu, 2006-08-17 at 19:11 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Revised patch enclosed, now believed to be production ready. This
implements regular log switching using the archive_timeout GUC.
Further patch enclosed implementing these changes plus the record type
On Fri, 2006-08-18 at 08:52 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2006-08-17 at 19:11 -0400, Tom Lane wrote:
I noticed a minor annoyance while testing: when the system is completely
idle, you get a forced segment switch every checkpoint_timeout seconds,
even
On Sat, 2006-09-02 at 09:14 -0400, Bruce Momjian wrote:
Simon Riggs wrote:
OK, I'll submit a C program called pg_standby so that we have an
approved and portable version of the script, allowing it to be
documented more easily.
I think we are still waiting for this. I am also waiting
-to data.
Seems like a great approach to this pain point.
More fun than lots of new datatypes also.
Is this an 8.2 thing? If not, is Numeric508 applied?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
. You need a full backend recompile
after changing it, but you shouldn't need to initdb, if that helps.
IIRC we did that already and the answer was 16...
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
and Lohman formula using the total tuples count (K *
inner_table_selectivity * inner_table_total_tuples).
I'd work on one thing at a time and go into it deeply.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
On Mon, 2006-09-11 at 14:25 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Is this an 8.2 thing?
You are joking, no?
Confirming, using an open question, and a smile.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end
On Wed, 2006-09-06 at 12:01 -0400, Bruce Momjian wrote:
Simon Riggs wrote:
1. Notes on restartable recovery
Previously submitted
2. Notes on standby functionality
3. discussion on rolling your own record-level polling using
pg_xlogfile_name_offset()
Given below, but not in SGML yet
On Tue, 2006-09-12 at 13:25 -0400, Andrew Dunstan wrote:
Simon Riggs wrote:
In general, log shipping between servers running different release
levels will not be possible. However, it may be possible for servers
running different minor release levels e.g. 8.2.1 and 8.2.2 to
inter
On Tue, 2006-09-12 at 16:23 -0400, Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] writes:
Simon Riggs [EMAIL PROTECTED] writes:
My memory is lousy at the best of times, but when have we had a minor
release that would have broken this due to changed format?
Not often, which is why I
, those tests seem reasonable to me so far.
These seem to be the beginnings of accurate wait time analysis, so I'm
listening closely.
Are you using a lightweight timer?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
() and pg_stop_backup() calls.
- Add support for forcing a switch to a new xlog file (Simon Riggs)
...should include Tom
- Improve performance of replaying WAL logs on a backup server (Simon
Riggs)
...I describe this as Restartable Recovery... don't think it improves
performance exactly, just avoids needing
On Fri, 2006-09-15 at 09:16 +0800, Golden Liu wrote:
this problem
I'm sorry but I don't see any problem. Why would you want to issue that
kind of SQL statement?
Assuming you really do, why not just DELETE/re-INSERT ?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
in tuplesort.c to support Windowed aggregates is:
ORDER BY foo (NULLS FIRST | NULLS LAST)
which we cannot yet specify.
I'm not planning to work on this just yet, but there's always next year.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
projects once each year and whichever way you cut it, 8.4 is a long way
off yet.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http
.
/para
/listitem
/orderedlist
/para
para
A weekly backup need only be taken once per week, yet the same level
of
protection is offered as if base backups were taken nightly.
/para
/sect2
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
Index
of personal time pressure yesterday: I
thought that made it clear that discussion was needed. Heikki mentions
to me it wasn't clear, so those criticisms are accepted.
On Tue, 2006-09-19 at 16:05 +0100, Heikki Linnakangas wrote:
Simon Riggs wrote:
+
+ if (startupAfterRecovery)
+ ereport(ERROR
.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
-defined aggregates now can take multiple columns as
inputs.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
for the
general reader and matches the docs.
Also, not sure what the thoughts are regarding surnames. I'm referred to
as both Simon and Simon Riggs in the release notes. Should we have a
policy of first mention uses full name, subsequent mentions just use
first name if there is no confusion by doing so
On Wed, 2006-09-20 at 18:22 +0200, Andreas Pflug wrote:
Simon Riggs wrote:
Zero administration overhead now possible (Alvaro)
With autovacuum enabled, all required vacuuming will now take place
without administrator intervention enabling wider distribution of
embedded databases
in favour of a Major Changes section.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your
of PostgreSQL, even if that specific module
has now been moved.
The release notes don't mention that the advisory locks feature has been
added either.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast
* COPY support for SELECT statements
change: COPY TO support ...
add to end of line: enhances data unload
* Array and aggregate improvements
add to end of line: , plus SQL:2003 statistical functions
--
Simon Riggs
is important when some
of the largest or most complex features are being considered.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
corrections by Thursday.
Suggested changes:
Warm Standby Databases
Online Index Builds: index builds occur while applications write to
database tables, allowing performance tuning without downtime
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
of matching rows in the sample, so Ndistinct estimates are
usually very poor for large Ndistinct. The estimates for low Ndistinct
are much better, so we can use them with a lower standard error to
correct the in-isolation estimate of other columns.
--
Simon Riggs
EnterpriseDB
(as you suggest)
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do
to change
this as part of beta, since we could easily cause more wierdness than we
solve.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http
word lists for their
languages. It seems a shame to have docs in so many languages, but no
language capability for Tsearch2.
Also, why do we have another crc32 implementation in there?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end
the usefulness of
multi-column indexes is much reduced anyhow, so cost/benefit not good.
Comments? (I'll do a summary of feedback tomorrow.)
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6
be improved.
/*+ Not on this thread, p-l-e-a-s-e */
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
as for a real index. As I mentioned, ideally
this would not be a full-strength catalog object, but I was thinking
towards implementation also. Another possibility would be to use a local
pg_virtual_indexes table.
On Tue, 2006-10-10 at 18:06 +0200, Peter Eisentraut wrote:
Simon Riggs wrote
On Fri, 2006-10-06 at 23:21 -0400, Bruce Momjian wrote:
I have added links from the 8.2 release notes into our documentation.
If people have additions/changes, please let me know.
Very cool.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
.
I would like to see some performance test results also. It would be good
to know whether they are fast/slow etc.. It will definitely help the
case for inclusion if they are faster than alternative multi-statement
approaches to solving the basic data access problems.
--
Simon Riggs www
. Instead, searchers that traverse down the tree will update
the upper pages when they see that they're out of sync. This should
alleviate the worry that we need to keep a bottom-level page exclusively
locked across I/O.
Thanks for taking time with the new FSM.
--
Simon Riggs www
page logic without fear of competition.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
a better way to
solve this problem, but I believe this patch would be useful for
regression testing.
It's possible to do this using planner hooks, so no patch needed.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list
implementation in for this release then I would urge we go for that,
rather than wait for perfection - as long as there are no other negative
effects.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers
On Tue, 2008-09-02 at 18:30 +0900, ITAGAKI Takahiro wrote:
Simon Riggs [EMAIL PROTECTED] wrote:
Why do we need to set rmgr_hook in _PG_init(), and add or mofify rmgrs
in our hook functions?
If we modify RmgrTable in _PG_init() then we would have to have that
structure available
so that it can't recover, you want to find out sooner
rather
than later when recovery is needed.
Great reason.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
Gorman, Wiscorp, that
The new standard was approved in early Summer. SQL 2008 is finished.
So as of now, SQL2008 exists, all hail. SQL2003 and earlier versions
have been superseded and can be ignored.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
On Tue, 2008-09-02 at 11:39 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
On Tue, 2008-09-02 at 18:30 +0900, ITAGAKI Takahiro wrote:
How about adding a new variable recovery_preload_libaries like as
shared_preload_libraries? Rmgr libs in it are loaded only in startup
On Tue, 2008-09-02 at 09:35 -0700, David Fetter wrote:
On Tue, Sep 02, 2008 at 12:42:45PM +0100, Simon Riggs wrote:
On Tue, 2008-09-02 at 03:14 -0400, Tom Lane wrote:
David Fetter [EMAIL PROTECTED] writes:
On Tue, Sep 02, 2008 at 02:42:25AM -0400, Tom Lane wrote:
It's not like we
to Postgres functions.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, 2008-09-03 at 09:51 +0300, Heikki Linnakangas wrote:
Simon Riggs wrote:
On Tue, 2008-09-02 at 15:51 +0300, Heikki Linnakangas wrote:
The needs of access to the rows are so different that it seems best to
me to delegate the buffering to the window function.
That seems
to these files?
src/include/storage/bufmgr.h
src/include/postmaster/bgwriter.h
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
the cost of an indexscan.
(What is the change to elog.c about?)
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref
or crash. In each of those cases its possible that we would have the
same conditions as exist at the end of WAL.
Can't see a failure case of importance though, just wanted to flag it up
as a possible. Better a false positive with these types of concern.
--
Simon Riggs www
of the tree, but that would wipe evidence that would be
useful in debugging.
We probably need to break out of infinite loops, especially ones that
output warning messages on each loop. :-)
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql
On Thu, 2008-09-04 at 11:12 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I notice that StartupCLOG zeroes out entries later than the nextxid when
we complete recovery in StartupXLOG, reason given is safety in case we
crash.
ISTM that we should also do that whenever we
On Thu, 2008-09-04 at 12:18 -0400, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
I was thinking about what happens when you are performing a PITR using
log records that contain a crash/recovery/shutdown checkpoint sequence.
I take it there's no problem there?
I don't really
On Thu, 2008-09-04 at 21:03 +0800, Xiao Meng wrote:
On Thu, Sep 4, 2008 at 10:06 AM, Simon Riggs [EMAIL PROTECTED]
wrote:
You don't give the text of the query used to do these
performance tests,
so I can't validate your test results.
The attachment
in general testing. There will always be cases where one
or the other is a winner, so having both will be useful.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes
901 - 1000 of 8408 matches
Mail list logo
