On Fri, Apr 30, 2010 at 12:56 AM, Takahiro Itagaki
itagaki.takah...@oss.ntt.co.jp wrote:
Jaime Casanova jcasa...@systemguards.com.ec wrote:
COPY is not working on latest HEAD?
regression=# select * from a;
aa
32
56
(2 rows)
regression=# COPY a TO '/tmp/copy_test';
COPY 0
Jaime Casanova jcasa...@systemguards.com.ec wrote:
ah! this is because COPY doesn't follow inherited tables... should it?
Yes. You can use COPY (SELECT * FROM a) TO instead to copy all tuples.
http://developer.postgresql.org/pgdocs/postgres/sql-copy.html
| COPY can only be used with plain
On Fri, Apr 30, 2010 at 1:13 AM, Takahiro Itagaki
itagaki.takah...@oss.ntt.co.jp wrote:
Jaime Casanova jcasa...@systemguards.com.ec wrote:
ah! this is because COPY doesn't follow inherited tables... should it?
Yes. You can use COPY (SELECT * FROM a) TO instead to copy all tuples.
On Fri, Apr 30, 2010 at 12:03 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Jaime Casanova jcasa...@systemguards.com.ec writes:
i was trying recent HS and get this when trying to start the standby,
TRAP: FailedAssertion(!(( (metabuffer) != 0 (metabuffer) =
-NLocBuffer (metabuffer) = NBuffers )),
Jaime Casanova wrote:
i was trying recent HS and get this when trying to start the standby,
actually i was expecting a crash because i use full_page_writes=off
and i guess it won't work.
Maybe we could say full_page_writes=off and wal_level=hot_standby are
conflicting and avoid such setup?
On tor, 2010-04-29 at 17:34 -0400, Bruce Momjian wrote:
I talked to a few people personally about this, and it seems there was a
misunderstanding. I was not asking if pg_migrator should be in 9.0
beta1. I was asking if we should think about putting it into a later
9.0 beta, like 9.0 beta3.
I've been working on a brute force method of saving view and function
source when changes to an underlying object force that object to be
dropped. But I think there is a way for Postgres to handle this that
wouldn't be too hard to implement and would be extremely useful for us
users.
Scott Bailey arta...@comcast.net wrote:
Problem: We need to change the last_name column of the people table from
varchar(30) to varchar(50).
Proposal: Add an invalid flag to pg_class.
Your example is one of the simplest cases, but there are other complex
usages. For example, shrinking
Peter Eisentraut pete...@gmx.net writes:
My personal feeling is that pg_migrator should be fully integrated, but
it's too late for that, obviously. Let's do it for 9.1.
+1
I also think that the standards for contrib should not be so lax that a
completely new module can be added after beta.
Hi all,
Please accept attached patch for the following problem.
af...@aftab-laptop:/opt/dev/pgsql/install/dbserver/bin$
af...@aftab-laptop:/opt/dev/pgsql/install/dbserver/bin$ ./psql postgres
psql (9.0beta1)
Type help for help.
postgres=# SHOW timezone;
TimeZone
--
Asia/Karachi
I think postgres git repo is broken.
The compilation of REL7_4_STABLE from git fails on my system with:
make -C src all
make -C port all
make[2]: *** No rule to make target `sprompt.o', needed by `libpgport.a'. Stop.
There is no sprompt.c in src/port in the sources obtained from git. However,
Alexey Klyukin wrote:
I think postgres git repo is broken.
The compilation of REL7_4_STABLE from git fails on my system with:
make -C src all
make -C port all
make[2]: *** No rule to make target `sprompt.o', needed by `libpgport.a'. Stop.
There is no sprompt.c in src/port in the sources
2010/4/30 Jaime Casanova jcasa...@systemguards.com.ec:
On Fri, Apr 30, 2010 at 1:13 AM, Takahiro Itagaki
itagaki.takah...@oss.ntt.co.jp wrote:
Jaime Casanova jcasa...@systemguards.com.ec wrote:
ah! this is because COPY doesn't follow inherited tables... should it?
Yes. You can use COPY
2010/4/30 Stefan Kaltenbrunner ste...@kaltenbrunner.cc:
Alexey Klyukin wrote:
I think postgres git repo is broken.
The compilation of REL7_4_STABLE from git fails on my system with:
make -C src all
make -C port all
make[2]: *** No rule to make target `sprompt.o', needed by `libpgport.a'.
On Fri, 2010-04-30 at 09:35 +0300, Heikki Linnakangas wrote:
Hmm, I see a bug in btree_redo handling of XLOG_BTREE_REUSE_PAGE. If
hot standby is not enabled in the standby, it chokes on that record
type. It's missing from btree_desc too.
Yep, correct fix.
This demonstrates that there really
Cédric Villemain wrote:
2010/4/30 Stefan Kaltenbrunner ste...@kaltenbrunner.cc:
I don't think the git repo was ever considered working for the backbranches
at all...
Really ?!
Then we have to remove the backbranches from the git.
On Fri, Apr 30, 2010 at 3:33 AM, Scott Bailey arta...@comcast.net wrote:
Proposal: Add an invalid flag to pg_class. Invalid objects would be ignored
when doing dependency checks for DDL statements. And an exception would be
thrown when an invalid object is called.
This is similar to what
Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
We can artificially make this problem as complicated as we wish, but
the people who are asking for this feature (including me) will, I
believe, be quite happy with a solution that throws, say, a NOTICE
instead of an ERROR when the
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Cédric Villemain wrote:
2010/4/30 Stefan Kaltenbrunner ste...@kaltenbrunner.cc:
I don't think the git repo was ever considered working for the backbranches
at all...
Really ?!
Then we have to remove the backbranches from the
Scott Bailey arta...@comcast.net writes:
Proposal: Add an invalid flag to pg_class. Invalid objects would be
ignored when doing dependency checks for DDL statements. And an
exception would be thrown when an invalid object is called.
IMO, the way Oracle does this pretty much sucks, and
Dimitri Fontaine dfonta...@hi-media.com writes:
Peter Eisentraut pete...@gmx.net writes:
I also think that the standards for contrib should not be so lax that a
completely new module can be added after beta. (This is mostly informed
by the feeling that contrib should go away entirely.)
+1
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Cédric Villemain wrote:
2010/4/30 Stefan Kaltenbrunner ste...@kaltenbrunner.cc:
I don't think the git repo was ever considered working for the backbranches
at all...
Really ?!
Then we
Tom Lane wrote:
Dimitri Fontaine dfonta...@hi-media.com writes:
Peter Eisentraut pete...@gmx.net writes:
I also think that the standards for contrib should not be so lax that a
completely new module can be added after beta. (This is mostly informed
by the feeling that contrib should
On fre, 2010-04-30 at 10:45 -0400, Tom Lane wrote:
In the end, the main useful function that contrib serves is to provide
examples of how to write Postgres extensions.
Maybe, but pg_migrator surely doesn't fit that. And neither does about
a third of the other contrib modules, IMO.
Because of
Andrew Dunstan and...@dunslane.net wrote:
If any Ruby hacker feels like fixing it please speak up.
I can't take it on any time soon. If nobody else picks it up, I can
get to it eventually. Anyone taking it on might want to read
through the thread which starts at:
On Fri, Apr 30, 2010 at 8:08 AM, Robert Haas robertmh...@gmail.com wrote:
On Fri, Apr 30, 2010 at 3:33 AM, Scott Bailey arta...@comcast.net wrote:
Proposal: Add an invalid flag to pg_class. Invalid objects would be ignored
when doing dependency checks for DDL statements. And an exception would
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If you aren't archiving then there's no guarantee that you'll still have
a continuous WAL series starting from the start of the backup.
I wasn't really thinking of this use case, but you could
Heikki Linnakangas wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Browsing the history of XLOG_PAGE_MAGIC, it used to be incremented by
one whenever the format changes, at least as long as it has been been in
xlog_internal.h. It started at 0xD05B in
On Fri, Apr 30, 2010 at 12:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If you aren't archiving then there's no guarantee that you'll still have
a continuous WAL series starting from the start of
Robert Haas wrote:
On Fri, Apr 30, 2010 at 12:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If you aren't archiving then there's no guarantee that you'll still have
a continuous WAL series
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be changed without restarting, right?)
Should we allow -1 to mean keep all segments?
Why is that not called max_wal_segments? wal_keep_segments sounds like
its been through Google translate.
--
Simon Riggs
Kevin Grittner wrote:
The reported source of the software seems to have gone away. I can
let you have my copy, which reliably reproduces the error, so we
have a good failure test case.
If it's not as recent as this:
http://ww2.fs.ei.tum.de/~corecode/hg/fromcvs/log/132
we might
Simon Riggs wrote:
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be changed without restarting, right?)
Should we allow -1 to mean keep all segments?
Why is that not called max_wal_segments? wal_keep_segments sounds like
its been through Google
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be changed without restarting, right?)
Should we allow -1 to mean keep all segments?
Why is that not called max_wal_segments?
On Fri, Apr 30, 2010 at 1:39 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Fri, Apr 30, 2010 at 12:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If you aren't archiving then
On 04/30/2010 01:53 PM, Robert Haas wrote:
Well, one of us is. Why would you want to retain all of your WAL logs
in pg_xlog forever?
...Robert
To create or re-synchronize SR slaves, one could change
wal_keep_segments to -1, run a backup, wait for the slaves to catch up,
and change it
Robert Haas wrote:
On Fri, Apr 30, 2010 at 1:39 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Fri, Apr 30, 2010 at 12:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If
On Fri, 2010-04-30 at 13:52 -0400, Robert Haas wrote:
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be changed without restarting, right?)
Should we allow -1 to mean keep all
On Fri, 2010-04-30 at 13:58 -0400, Bruce Momjian wrote:
Robert Haas wrote:
On Fri, Apr 30, 2010 at 1:39 PM, Bruce Momjian br...@momjian.us wrote:
Robert Haas wrote:
On Fri, Apr 30, 2010 at 12:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Heikki Linnakangas
Andrew Dunstan and...@dunslane.net writes:
Quite so. Getting a better extensions mechanism doesn't mean we should
abandon what we currently have, IMNSHO.
Yeah, agreed. Exactly what I proposed. The only change is the
distribution mean. Either we keep things as they are now exactly, or we
use the
Robert Haas wrote:
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be changed without restarting, right?)
Should we allow -1 to mean keep all segments?
Why is that not called
Bruce Momjian wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If you aren't archiving then there's no guarantee that you'll still have
a continuous WAL series starting from the start of the backup.
I wasn't really thinking of this use
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Yeah, min_wal_segments or something would make sense.
Surely it would confuse people to see they have fewer than
min_wal_segments WAL segments.
-Kevin
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To
Heikki Linnakangas wrote:
Robert Haas wrote:
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be changed without restarting, right?)
Should we allow -1 to mean keep all segments?
Why
Bruce Momjian wrote:
Heikki Linnakangas wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Browsing the history of XLOG_PAGE_MAGIC, it used to be incremented by
one whenever the format changes, at least as long as it has been been in
xlog_internal.h. It
Robert Haas robertmh...@gmail.com writes:
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
Why is that not called max_wal_segments? wal_keep_segments sounds like
its been through Google translate.
Because it's not a maximum?
Indeed. It would really be more like
Heikki Linnakangas wrote:
Bruce Momjian wrote:
Tom Lane wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Tom Lane wrote:
If you aren't archiving then there's no guarantee that you'll still have
a continuous WAL series starting from the start of the backup.
I
On Fri, Apr 30, 2010 at 2:08 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2010-04-30 at 13:52 -0400, Robert Haas wrote:
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Fri, 2010-04-30 at 12:22 -0400, Bruce Momjian wrote:
(wal_keep_segments can be
Heikki Linnakangas heikki.linnakan...@enterprisedb.com writes:
Bruce Momjian wrote:
Should we allow -1 to mean keep all segments?
Umm, you can't keep all segments around forever, can you? Surely you
have to recycle them sooner or later or you will run out of disk space.
You couldn't use that
Bruce Momjian escribió:
Which is where my 'wal_keep_segments = -1' idea came from.
Are you suggesting that -1 should mean keep all segments that fit on
disk, but if creating a new segment fails with ENOSPC, recycle the
oldest one?
--
Alvaro Herrera
Michael Tharp wrote:
On 04/30/2010 01:53 PM, Robert Haas wrote:
Well, one of us is. Why would you want to retain all of your WAL logs
in pg_xlog forever?
To create or re-synchronize SR slaves, one could change
wal_keep_segments to -1, run a backup, wait for the slaves to catch up,
and
Alvaro Herrera alvhe...@commandprompt.com writes:
Bruce Momjian escribió:
Which is where my 'wal_keep_segments = -1' idea came from.
Are you suggesting that -1 should mean keep all segments that fit on
disk, but if creating a new segment fails with ENOSPC, recycle the
oldest one?
No, keep
On Fri, 2010-04-30 at 14:42 -0400, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Apr 30, 2010 at 1:44 PM, Simon Riggs si...@2ndquadrant.com wrote:
Why is that not called max_wal_segments? wal_keep_segments sounds like
its been through Google translate.
Because it's
Kevin Grittner wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Yeah, min_wal_segments or something would make sense.
Surely it would confuse people to see they have fewer than
min_wal_segments WAL segments.
Umm, they wouldn't see that, that's the point of the
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Kevin Grittner wrote:
Surely it would confuse people to see they have fewer than
min_wal_segments WAL segments.
they wouldn't see that, that's the point of the setting.
I was thinking, in particular, about beginners poking
Jaime Casanova jcasa...@systemguards.com.ec writes:
COPY is not working on latest HEAD?
I've added this to the COPY notes section:
para
commandCOPY/command only deals with the specific table named;
it does not copy data to or from child tables. Thus for example
literalCOPY
While playing with HS/SR on -HEAD I noticed that setting
setting max_standby_delay to -1 leads to the following kind of odd ps
display:
1000 20254 9.2 11.3 8625164 5600644 ? Rs 21:22 1:50
postgres: startup process waiting for max_standby_delay (4294967295 s)
This seems
Please add it to the next commit-fest:
https://commitfest.postgresql.org/action/commitfest_view/inprogress
---
z...@cybertec.at wrote:
Resending, my ISP lost my mail yesterday. :-(
Stefan Kaltenbrunner ste...@kaltenbrunner.cc writes:
While playing with HS/SR on -HEAD I noticed that setting
setting max_standby_delay to -1 leads to the following kind of odd ps
display:
1000 20254 9.2 11.3 8625164 5600644 ? Rs 21:22 1:50
postgres: startup process waiting
Tom Lane wrote:
Dimitri Fontaine dfonta...@hi-media.com writes:
Peter Eisentraut pete...@gmx.net writes:
I also think that the standards for contrib should not be so lax that a
completely new module can be added after beta. (This is mostly informed
by the feeling that contrib should go
60 matches
Mail list logo
