Magnus Hagander wrote:
I discussed this briefly with Robert on IM yesterday - he told me the
account was installer created. Without a PC at the time I couldn't look
into it further :-(
The faq still applies as the most likely reason. It can certainly happen
with the installer created
On Fri, Jan 05, 2007 at 08:30:58AM +, Dave Page wrote:
Magnus Hagander wrote:
I discussed this briefly with Robert on IM yesterday - he told me the
account was installer created. Without a PC at the time I couldn't look
into it further :-(
The faq still applies as the most likely
I am working on support scrollable cursors in plpgpsm. Scrollable
cursors
are in ToDo for plpgsql too. I need new function
SPI_cursor_fetch_with_direction(Portal portal, int direction, long
count)
Is int a reasonable domain for directions? I'd think there would
be
at most
Tom Lane wrote:
I think the context for this is that you have an agreed-on maintenance
window, say extending from 2AM to 6AM local time, and you want to get
all your vacuuming done in that window without undue spikes in the
system load (because you do still have live users then, just not as
Andrew Dunstan wrote:
Gavin Sherry wrote:
With PLM, you could test patches against various code branches. I'd
guessed Mark would want to provide this capability. Pulling branches from
anonvcvs regularly might be burdensome bandwidth-wise. So, like you say, a
local mirror would be beneficial for
Recovery can occur with/without same setting of wal_checksum, to
avoid
complications from crashes immediately after turning GUC on.
Surely not. Otherwise even the on setting is not really a
defense.
Only when the CRC is exactly zero, which happens very very rarely.
It
On Fri, 2007-01-05 at 11:01 +0100, Zeugswetter Andreas ADI SD wrote:
What's the use-case for changing the variable on the fly anyway? Seems a
better
solution is just to lock down the setting at postmaster start.
I guess that the use case is more for a WAL based replicate, that
What's the use-case for changing the variable on the fly anyway?
Seems a
better
solution is just to lock down the setting at postmaster start.
I guess that the use case is more for a WAL based replicate, that
has/wants a different setting. Maybe we want a WAL entry for the
Galy Lee [EMAIL PROTECTED] writes:
It is true that there is not a decent way to estimate the amount of work
to be done. But the purpose in here is not âspread the vacuum over 6
hours exactlyâ, it is âfinish vacuum within 6 hours, and spread the
spikes as much as possibleâ. So the
Tino Wildenhain wrote:
[EMAIL PROTECTED] schrieb:
On 1/4/07, Gavin Sherry [EMAIL PROTECTED] wrote:
On Thu, 4 Jan 2007, Andrew Dunstan wrote:
...
Pulling branches from
anonvcvs regularly might be burdensome bandwidth-wise. So, like you
say, a
local mirror would be beneficial for patch
Zeugswetter Andreas ADI SD [EMAIL PROTECTED] writes:
Ok, so when you need CRC's on a replicate (but not on the master) you
turn it
off during standby replay, but turn it on when you start the replicate
for normal operation.
Thought: even when it's off, the CRC had better be computed for
Heikki Linnakangas [EMAIL PROTECTED] writes:
I believe it would actually be even better to combine the t_natts and
t_infomask fields to a single 32-bit infomask field.
That's not happening, because the alignment is wrong ...unless maybe
we switch this field to fall before t_ctid, but that
Ok, so when you need CRC's on a replicate (but not on the master)
you
turn it
off during standby replay, but turn it on when you start the
replicate
for normal operation.
Thought: even when it's off, the CRC had better be computed for
shutdown-checkpoint records. Else there's no way
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of entire clusters as
well as role and tablespace definitions, we need to be able to get
pg_dumpall to write
As far as I can see, adding a -f option to pg_dumpall should be straight
forward, the only issue being that we'd need to pass pg_dump an
additional (undocumented?) option to tell it to append to the output
file instead of writing it as normal.
Any thoughts or better ideas?
Yeah :) Getting
Dave Page wrote:
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of entire clusters as
well as role and tablespace definitions, we need to be able to get
On Friday 05 January 2007 09:40, Andrew Dunstan wrote:
Dave Page wrote:
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of entire clusters as
well
I have the pleasure of announcing your PGCon 2007 program committee.
Bruce Momjian
Christopher Browne
Josh Berkus
Robert Treat
Luke Lonergan
Neil Conway
Robert Bernier
These people are responsible for reviewing your submissions and
selecting the presentations for PGCon 2007.
Speaking of
On Fri, Jan 05, 2007 at 12:40:20PM -0500, Andrew Dunstan wrote:
Dave Page wrote:
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of entire clusters as
On Jan 4, 2007, at 13:33 , Tom Lane wrote:
Another possible objection is that in the proposed CREATE INDEX syntax
index-column-id [ opclass-name ] [ DESC ] [ NULLS {FIRST|LAST} ]
DESC must be a fully reserved word else it can't be distinguished from
an opclass name. But guess what,
David Fetter wrote:
This seems a bit like piecemeal reform. Here are some things I'd like to
see that affect this area:
. merge pg_dump and pg_dumpall (e.g. add a flag to pg_dump that says do
the lot)
. multi-db non-text dumps
And while we're about it, can we teach pg_restore to handle text
Andreas Pflug wrote:
Dave Page wrote:
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of entire clusters as
well as role and tablespace definitions, we
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
What value is allowing multiple queies via PQexec()
The only argument I can think of is that it allows applications to be
sloppy about parsing a SQL script into individual commands before they
send it. (I think initdb may be guilty of
Michael Glaesemann [EMAIL PROTECTED] writes:
On Jan 4, 2007, at 13:33 , Tom Lane wrote:
index-column-id [ opclass-name ] [ DESC ] [ NULLS {FIRST|LAST} ]
DESC must be a fully reserved word else it can't be distinguished from
an opclass name. But guess what, it already is.
A point in favor
Bruce Momjian wrote:
Log Message:
---
Stamp major release 8.3.0, and increment library version numbers.
this commit broke the buildfarm(ECPG-checks):
http://www.pgbuildfarm.org/cgi-bin/show_status.pl
Stefan
---(end of broadcast)---
Stefan Kaltenbrunner wrote:
Bruce Momjian wrote:
Log Message:
---
Stamp major release 8.3.0, and increment library version numbers.
this commit broke the buildfarm(ECPG-checks):
http://www.pgbuildfarm.org/cgi-bin/show_status.pl
Thanks, fixed.
--
Bruce Momjian [EMAIL
Dave Page [EMAIL PROTECTED] writes:
As far as I can see, adding a -f option to pg_dumpall should be straight
forward, the only issue being that we'd need to pass pg_dump an
additional (undocumented?) option to tell it to append to the output
file instead of writing it as normal.
Wouldn't it
Dave Page [EMAIL PROTECTED] writes:
Hmm, well I have no interest in the latter at present, but assuming the
powers that be will allow me some time to do so, I will look at merging
pg_dump and pg_dumpall as that seems to be the way people want to go.
I think this will be an exercise in
Bruce Momjian [EMAIL PROTECTED] writes:
Stefan Kaltenbrunner wrote:
Bruce Momjian wrote:
Stamp major release 8.3.0, and increment library version numbers.
this commit broke the buildfarm(ECPG-checks):
http://www.pgbuildfarm.org/cgi-bin/show_status.pl
Thanks, fixed.
The idea of having to
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
Stefan Kaltenbrunner wrote:
Bruce Momjian wrote:
Stamp major release 8.3.0, and increment library version numbers.
this commit broke the buildfarm(ECPG-checks):
http://www.pgbuildfarm.org/cgi-bin/show_status.pl
Thanks,
Tom Lane schrieb:
Dave Page [EMAIL PROTECTED] writes:
As far as I can see, adding a -f option to pg_dumpall should be straight
forward, the only issue being that we'd need to pass pg_dump an
additional (undocumented?) option to tell it to append to the output
file instead of writing it as
Simon Riggs wrote:
On Thu, 2007-01-04 at 16:01 -0500, Bruce Momjian wrote:
Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Minor request for clarification:
I read in the Developer's FAQ that tabs should be interpreted as 4
spaces. ...and also that pgindent replaces tabs as
Dave Page wrote:
In pgAdmin we use pg_dump's -f option to write backup files. The IO
streams are redirected to display status and errors etc. in the GUI.
In order to enhance the interface to allow backup of entire clusters as
well as role and tablespace definitions, we need to be able to get
On Tue, Jan 02, 2007 at 10:04:43AM -0500, Andrew Dunstan wrote:
Jim C. Nasby wrote:
On Mon, Jan 01, 2007 at 06:30:40PM -0600, Andrew Dunstan wrote:
Tom Lane wrote:
Jim C. Nasby [EMAIL PROTECTED] writes:
FWIW, I'm running into this trying to create a 'raw' domain that would
I've run into an annoying parsing problem while working on the NULLS
FIRST/LAST stuff. It turns out this is ambiguous:
... ORDER BY foo! NULLS ...
It could be that the ! is a postfix operator and the NULLS is the
start of a NULLS FIRST/LAST clause, or it could be that the ! is an
infix
Ron Mayer [EMAIL PROTECTED] writes:
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
What value is allowing multiple queies via PQexec()
The only argument I can think of is that it allows applications to be
sloppy about parsing a SQL script into individual commands before they
send
On Jan 4, 2007, at 7:54 PM, Simon Riggs wrote:
On Thu, 2007-01-04 at 21:41 -0300, Alvaro Herrera wrote:
Simon Riggs wrote:
S'OK, just thought it was funny I'd been doing it backwards all this
time: Actively been replacing tabs with spaces. :-)
That explains why your patches always seemed to
On Jan 4, 2007, at 11:30 PM, Bruce Momjian wrote:
No, psql isn't the point: we can certainly make its behavior match
the
backend's. What I'm wondering about is the effect on random PG-using
applications: should we forbid them from sending multiple SQL
commands
per PQexec (or equivalent in
On Jan 5, 2007, at 10:24 AM, Andrew Dunstan wrote:
cvs update isn't too bad either. I just did a substantial update on
a tree that had not been touched for nearly 6 months, and ethereal
tells me that total traffic was 7343004 bytes in 7188 packets.
Individual buildfarm updates are going to
On Jan 5, 2007, at 6:30 AM, Zeugswetter Andreas ADI SD wrote:
Ok, so when you need CRC's on a replicate (but not on the master) you
turn it
off during standby replay, but turn it on when you start the replicate
for normal operation.
Which sounds to me like a good reason to allow the option in
On Jan 3, 2007, at 11:42 PM, ITAGAKI Takahiro wrote:
BTW, if we want to achieve the index-only scan, we might have to do
more
aggressive VACUUM FREEZE. There were many comments that we should
avoid
vacuuming pages that contain only unfrozen tuples or a few dead
tuples.
I think it it true
On Jan 3, 2007, at 4:20 PM, Bill Moran wrote:
* trace_temp_files is now an int: -1 disables, 0 and up equate to
log if
the file is this size or larger
Another thought is to allow ignoring files over a certain size. The
reason is that if you end up creating 10MB of temp files, you can
Gurjeet Singh [EMAIL PROTECTED] writes:
This patch removes double-quotes from around the listen_addresses=%s part; I
couldn't find a way of doing that. But then, the questions is, can the %s
(hostname) have spaces embedded in it?
Yes, because it can be more than one hostname. Why do you want
Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
What value is allowing multiple queies via PQexec()
The only argument I can think of is that it allows applications to be
sloppy about parsing a SQL script into individual commands before they
send it. (I think initdb may be guilty
Jim Nasby wrote:
On Jan 5, 2007, at 10:24 AM, Andrew Dunstan wrote:
cvs update isn't too bad either. I just did a substantial update on
a tree that had not been touched for nearly 6 months, and ethereal
tells me that total traffic was 7343004 bytes in 7188 packets.
Individual buildfarm
Jim Nasby [EMAIL PROTECTED] writes:
On Jan 5, 2007, at 6:30 AM, Zeugswetter Andreas ADI SD wrote:
Ok, so when you need CRC's on a replicate (but not on the master) you
Which sounds to me like a good reason to allow the option in
recovery.conf as well...
Actually, I'm not seeing the
Actually, I'm not seeing the use-case for a slave having a different
setting from the master at all?
My backup server is less reliable than the primary.
My backup server is more reliable than the primary.
Somehow, neither of these statements seem likely to be uttered by
a
Andrew Dunstan [EMAIL PROTECTED] writes:
Jim Nasby wrote:
More important, I see no reason to tie applying patches to pulling
from CVS. In fact, I think it's a bad idea: you want to build just
what's in CVS first, to make sure that it's working, before you start
testing any patches against it.
On 1/6/07, Tom Lane [EMAIL PROTECTED] wrote:
Gurjeet Singh [EMAIL PROTECTED] writes:
This patch removes double-quotes from around the listen_addresses=%s
part; I
couldn't find a way of doing that. But then, the questions is, can the
%s
(hostname) have spaces embedded in it?
Yes, because it
Tom Lane wrote:
Andrew Dunstan [EMAIL PROTECTED] writes:
Jim Nasby wrote:
More important, I see no reason to tie applying patches to pulling
from CVS. In fact, I think it's a bad idea: you want to build just
what's in CVS first, to make sure that it's working, before you start
testing any
Gurjeet Singh [EMAIL PROTECTED] writes:
On 1/6/07, Tom Lane [EMAIL PROTECTED] wrote:
Yes, because it can be more than one hostname.
But the code in postmaster.c expects the list to be comma separated.
Sure, but SplitIdentifierString allows for whitespace, eg
'host1, host2, host3'
51 matches
Mail list logo
