On 29.09.2010 10:56, Fujii Masao wrote:
On Wed, Sep 29, 2010 at 11:47 AM, Robert Haasrobertmh...@gmail.com wrote:
So we've got two patches that implement synchronous replication, and
no agreement on which one, if either, should be committed. We have no
agreement on how synchronous replication
On tor, 2010-09-30 at 08:09 +0900, Tatsuo Ishii wrote:
Problem with 9.0 doc build system is now it's a mixture of
DocBook/SGML *and* DocBook/XML(used for man pages). The former *only*
accepts EUC-JP, the latter *only* accepts UTF-8. So we are stuck.
How do you get to the conclusion that
On 30.09.2010 04:30, Itagaki Takahiro wrote:
On Wed, Sep 29, 2010 at 11:09 PM, Alvaro Herrera
alvhe...@commandprompt.com wrote:
I'm not sure that it's a good idea to embed into the FDW API the set of
operations known to the executor. For example your proposal fails to
consider bitmap scans.
On 29 September 2010 20:18, Bernd Helmle maili...@oopsware.de wrote:
--On 8. September 2010 09:00:33 +0100 Dean Rasheed
dean.a.rash...@gmail.com wrote:
Here's an updated version with improved formatting and a few minor
wording changes to the triggers chapter.
This version doesn't apply
Excerpts from Peter Eisentraut's message of mié sep 29 04:08:35 -0400 2010:
On sön, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote:
Yeah, that's what you need to do. I would guess you were previously
subscribed as pe...@postgresql.org, but the git commit scrpit sends
the email from
On Wed, 29 Sep 2010, Alvaro Herrera wrote:
Excerpts from Peter Eisentraut's message of mi? sep 29 04:08:35 -0400 2010:
On s?n, 2010-09-26 at 17:11 +0200, Magnus Hagander wrote:
Yeah, that's what you need to do. I would guess you were previously
subscribed as pe...@postgresql.org, but the
On Thu, 30 Sep 2010 09:26:54 +0300
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
FYI, HiRDB, that implements FDW routines, has CREATE FOREIGN INDEX.
I think it is a little ugly and won't work in some cases -- for example,
index organized tables -- but evidently it's a
Hello
This patch add iteration over array to plpgsql
now is supported only iteration over scalar array
Regards
Pavel Stehule
*** ./gram.y.orig 2010-09-29 10:53:44.663270537 +0200
--- ./gram.y 2010-09-30 09:04:04.809900052 +0200
***
*** 239,244
--- 239,245
%token keyword
On Thu, Sep 30, 2010 at 04:40, Itagaki Takahiro
itagaki.takah...@gmail.com wrote:
Hi, I have a question about the latest patch.
On Sun, Aug 22, 2010 at 11:03 PM, Quan Zongliang
quanzongli...@gmail.com wrote:
New patch attached. How about this?
I don't see us ever using anything other than
On Thu, 2010-09-30 at 09:09 +0300, Heikki Linnakangas wrote:
On 29.09.2010 10:56, Fujii Masao wrote:
On Wed, Sep 29, 2010 at 11:47 AM, Robert Haasrobertmh...@gmail.com wrote:
This feature is important, and we need to get it done. How do we get
the ball rolling again?
Agreed. Actually,
--On 29. September 2010 23:05:11 -0400 Andrew Geery
andrew.ge...@gmail.com wrote:
Reference: https://commitfest.postgresql.org/action/patch_view?id=312
The patch from
http://archives.postgresql.org/message-id/ca2e4c4762eae28d68404...@amenop
his does not apply cleanly to the current git
sorry
fixed patch
Pavel
2010/9/30 Pavel Stehule pavel.steh...@gmail.com:
Hello
This patch add iteration over array to plpgsql
now is supported only iteration over scalar array
Regards
Pavel Stehule
*** ./gram.y.orig 2010-09-29 10:53:44.663270537 +0200
--- ./gram.y 2010-09-30
On Wed, Sep 29, 2010 at 23:45, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Magnus Hagander mag...@hagander.net wrote:
Comments and contributions are most welcome.
This is probably too esoteric to be worked on yet, but for this to
be useful for us we would need to pass the resulting
Hello
2010/9/28 Robert Haas robertmh...@gmail.com:
On Tue, Sep 7, 2010 at 12:55 PM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2010/9/7 Teodor Sigaev teo...@sigaev.ru:
Hm, what is aim of this hook? It looks like a wrapper of dictionary init
method.
If I use a mmap for shared dictionary,
Ok -- I've updated the commitfest page linking in this review and
changing the status to waiting on a new patch from you.
Thanks
Andrew
On Thu, Sep 30, 2010 at 4:12 AM, Bernd Helmle maili...@oopsware.de wrote:
--On 29. September 2010 23:05:11 -0400 Andrew Geery andrew.ge...@gmail.com
wrote:
Hello
this patch implement a new iteration construct - iteration over an
array. The sense of this new iteration is:
* a simple and cleaner syntax
* a faster execution - this bring down a number of detoast operations
create or replace function subscripts(anyarray, int)
returns int[] as $$
On Thu, Sep 30, 2010 at 09:14:42AM +0100, Simon Riggs wrote:
On Thu, 2010-09-30 at 09:09 +0300, Heikki Linnakangas wrote:
On 29.09.2010 10:56, Fujii Masao wrote:
On Wed, Sep 29, 2010 at 11:47 AM, Robert Haasrobertmh...@gmail.com
wrote:
This feature is important, and we need to get
Magnus Hagander mag...@hagander.net wrote:
If you could keep the development friendly to such features, I
may get around to adding them to support our needs
Would it be enough to have kind of an archive_command switch
that says whenever you've finished a complete wal segment, run
this
David Fetter da...@fetter.org writes:
On Thu, Sep 30, 2010 at 09:14:42AM +0100, Simon Riggs wrote:
I don't see anything has stalled.
I do. We're half way through this commitfest, so if no one's actually
ready to commit one of the patches, I kinda have to bounce them both,
at least to the
On Thu, Sep 30, 2010 at 2:09 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Agreed. Actually, given the lack of people jumping in and telling us what
they'd like to do with the feature, maybe it's not that important after all.
The basic features that I mean is for most
On Thu, Sep 30, 2010 at 09:52:46AM -0400, Tom Lane wrote:
David Fetter da...@fetter.org writes:
On Thu, Sep 30, 2010 at 09:14:42AM +0100, Simon Riggs wrote:
I don't see anything has stalled.
I do. We're half way through this commitfest, so if no one's
actually ready to commit one of
Aidan Van Dyk ai...@highrise.ca wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
I'm sure there's several things you can accomplish with
synchronous replication, perhaps you could describe what the
important use case for you is?
I'm looking for data durability, not
On 30.09.2010 17:09, Kevin Grittner wrote:
Aidan Van Dykai...@highrise.ca wrote:
Heikki Linnakangasheikki.linnakan...@enterprisedb.com wrote:
I'm sure there's several things you can accomplish with
synchronous replication, perhaps you could describe what the
important use case for you is?
On Thu, Sep 30, 2010 at 15:45, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Magnus Hagander mag...@hagander.net wrote:
If you could keep the development friendly to such features, I
may get around to adding them to support our needs
Would it be enough to have kind of an
On 29.09.2010 11:46, Fujii Masao wrote:
Aside from standby registration itself, I have another thought for C). Keeping
many WAL files in pg_xlog of the master is not good design in the first place.
I cannot believe that pg_xlog in most systems has enough capacity to store many
WAL files for the
On Thu, Sep 30, 2010 at 10:24 AM, Magnus Hagander mag...@hagander.net wrote:
That would allow some nice options. I've been thinking what would
be the ideal use of this with our backup scheme, and the best I've
thought up would be that each WAL segment file would be a single
output stream,
Heikki Linnakangas wrote:
On 30.09.2010 17:09, Kevin Grittner wrote:
Aidan Van Dykai...@highrise.ca wrote:
Heikki Linnakangasheikki.linnakan...@enterprisedb.com wrote:
I'm sure there's several things you can accomplish with
synchronous replication, perhaps you could describe what the
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
You do realize that to be able to guarantee zero data loss, the
master will have to stop committing new transactions if the
streaming stops for any reason, like a network glitch. Maybe
that's a tradeoff you want, but I'm asking
On Thu, Sep 30, 2010 at 16:39, Aidan Van Dyk ai...@highrise.ca wrote:
On Thu, Sep 30, 2010 at 10:24 AM, Magnus Hagander mag...@hagander.net wrote:
That would allow some nice options. I've been thinking what would
be the ideal use of this with our backup scheme, and the best I've
thought up
Magnus Hagander mag...@hagander.net wrote:
We'd need a second script/command to call to figure out where to
restart from in that case, no?
I see your point; I guess we would need that.
It should be safe to just rsync the archive directory as it's
being written by pg_streamrecv. Doesn't
Aidan Van Dyk ai...@highrise.ca wrote:
When the being written to segmnt copmletes moves to the final
location, he'll get an extra whole copy of the file. But of the
move can be an exec of his scritpt, the compressed/gzipped final
result shouldn't be that bad. Certainly no worse then what
On Thu, 2010-09-30 at 07:06 -0700, David Fetter wrote:
On Thu, Sep 30, 2010 at 09:52:46AM -0400, Tom Lane wrote:
David Fetter da...@fetter.org writes:
On Thu, Sep 30, 2010 at 09:14:42AM +0100, Simon Riggs wrote:
I don't see anything has stalled.
I do. We're half way through this
On Wed, 2010-09-29 at 08:44 -0400, Alvaro Herrera wrote:
So, I think twice disk space of the sum of table and indexes would be
the simplest explanation for safe margin.
Agreed.
Surely the peak space is x3?
Old space + sort space + new space.
--
Simon Riggs
On Thu, Sep 30, 2010 at 12:52 PM, Simon Riggs si...@2ndquadrant.com wrote:
On Thu, 2010-09-30 at 07:06 -0700, David Fetter wrote:
On Thu, Sep 30, 2010 at 09:52:46AM -0400, Tom Lane wrote:
David Fetter da...@fetter.org writes:
On Thu, Sep 30, 2010 at 09:14:42AM +0100, Simon Riggs wrote:
I
2010/9/29 KaiGai Kohei kai...@ak.jp.nec.com:
In addition, I want to give these entrypoints its name which
represents an appropriate purpose of the hook, rather than
a uniformed one.
It sounds like you're proposing to create a vast number of hooks
rather than just one. If we have ~20 object
Simon Riggs si...@2ndquadrant.com writes:
On Wed, 2010-09-29 at 08:44 -0400, Alvaro Herrera wrote:
So, I think twice disk space of the sum of table and indexes would be
the simplest explanation for safe margin.
Agreed.
Surely the peak space is x3?
Old space + sort space + new space.
The
Jayant Kumar did some benchmarking of InnoDB vs. PostgreSQL and PG
came out 5 times faster. The benchmark isn't very thoroughly
described, but it turns out not to matter.
http://jayant7k.blogspot.com/2010/09/database-speed-tests-mysql-and.html
Apparently, the reason we're faster is that
Hello
The attached patch contains a implementation of subscripts function.
The functionality of this function is same like generate_subscripts
function, but it's based for iteration from plpgsql's for-in-array.
Regards
Pavel Stehule
*** ./doc/src/sgml/func.sgml.orig 2010-09-29
On Thu, Sep 30, 2010 at 8:26 PM, Robert Haas robertmh...@gmail.com wrote:
Jayant Kumar did some benchmarking of InnoDB vs. PostgreSQL and PG
came out 5 times faster. The benchmark isn't very thoroughly
described, but it turns out not to matter.
On Thu, Sep 30, 2010 at 8:26 PM, Robert Haas robertmh...@gmail.com wrote:
Jayant Kumar did some benchmarking of InnoDB vs. PostgreSQL and PG
came out 5 times faster. The benchmark isn't very thoroughly
described, but it turns out not to matter.
Attached are two versions of the same patch, with and without --patience.
The with-patience version has only two hunks, removal of a big block of
comment and addition of a big block of code.
The without-patience patience is riddled with the mix of two hunks, spread
until line 120.
--patience is
On Thu, Sep 30, 2010 at 4:09 PM, Dave Page dp...@pgadmin.org wrote:
On Thu, Sep 30, 2010 at 8:26 PM, Robert Haas robertmh...@gmail.com wrote:
Jayant Kumar did some benchmarking of InnoDB vs. PostgreSQL and PG
came out 5 times faster. The benchmark isn't very thoroughly
described, but it turns
On Wed, Sep 29, 2010 at 8:42 PM, Gurjeet Singh singh.gurj...@gmail.com wrote:
Attached is a patch that implements replacing a primary key with another
index. This would help overcome the limitation that primary keys cannot be
reindexed
without taking exclusive locks.
Sounds useful. You
Gurjeet Singh singh.gurj...@gmail.com wrote:
The with-patience version has only two hunks, removal of a big
block of comment and addition of a big block of code.
The without-patience patience is riddled with the mix of two
hunks, spread until line 120.
--patience is a clear winner here.
On Wed, Sep 29, 2010 at 2:45 PM, James Robinson
jlrob...@socialserve.com wrote:
Hackers,
Any tips / conventional wisdom regarding running postgres on
large-ish memory ccNUMA intel machines, such as a 32G dual-quad-core,
showing two NUMA nodes of 16G each? I expect each postgres
Robert Haas robertmh...@gmail.com writes:
Oh, I missed that. Actually, I wasn't really so concerned with
whether his benchmark is correct. I *am* concerned about being broken
out of the box on MacOS X.
Actually, the problem with OSX is that OSX is broken out of the box,
at least by that
On Sep 30, 2010, at 5:02 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
Oh, I missed that. Actually, I wasn't really so concerned with
whether his benchmark is correct. I *am* concerned about being broken
out of the box on MacOS X.
Actually, the problem with OSX is that
On Thu, Sep 30, 2010 at 5:02 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Oh, I missed that. Actually, I wasn't really so concerned with
whether his benchmark is correct. I *am* concerned about being broken
out of the box on MacOS X.
Actually, the
Can we please change the comment lines below the patch heading to have the
real name instead of the postgresql.org ID?
Patch by Pavel Stehule
Patch by Gurjeet Singh
instead of
Patch by okbobcz
Patch by singh.gurjeet
https://commitfest.postgresql.org/action/commitfest_view?id=8
Thanks,
--
On Thu, Sep 30, 2010 at 5:38 PM, Gurjeet Singh singh.gurj...@gmail.com wrote:
Can we please change the comment lines below the patch heading to have the
real name instead of the postgresql.org ID?
Patch by Pavel Stehule
Patch by Gurjeet Singh
instead of
Patch by okbobcz
Patch by
On Thu, Sep 30, 2010 at 11:45 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Sep 30, 2010 at 5:38 PM, Gurjeet Singh singh.gurj...@gmail.com
wrote:
Can we please change the comment lines below the patch heading to have
the
real name instead of the postgresql.org ID?
Patch by Pavel
On 09/30/2010 05:51 PM, Gurjeet Singh wrote:
On Thu, Sep 30, 2010 at 11:45 PM, Robert Haas robertmh...@gmail.com
mailto:robertmh...@gmail.com wrote:
On Thu, Sep 30, 2010 at 5:38 PM, Gurjeet Singh
singh.gurj...@gmail.com mailto:singh.gurj...@gmail.com wrote:
Can we please change
On Thu, Sep 30, 2010 at 5:51 PM, Gurjeet Singh singh.gurj...@gmail.com wrote:
On Thu, Sep 30, 2010 at 11:45 PM, Robert Haas robertmh...@gmail.com wrote:
On Thu, Sep 30, 2010 at 5:38 PM, Gurjeet Singh singh.gurj...@gmail.com
wrote:
Can we please change the comment lines below the patch
On Thu, Sep 30, 2010 at 2:22 PM, A.M. age...@themactionfaction.com wrote:
That is not correct. fsync and friends on Darwin synchronizes I/O and flushes
dirty kernel caches to the disk which meets the specification and is
distinctly different from doing nothing.
How exactly is it different
Attached is a patch to display getrusage output to EXPLAIN output.
This is the patch I mentioned previously in
http://archives.postgresql.org/pgsql-hackers/2010-02/msg00684.php and
it raises the same issues we were talking about then. Should the
resource usage stats displayed be per-iteration
On 9/29/10 7:54 PM, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
But that's not what Tom is talking about, I don't think: you might
also want a way to explicitly whack the flag in pg_control around.
That would probably be along the lines of pg_resetxlog. I'm not sure
how much
Tom Lane wrote:
I'm not sure whether we should select fsync_writethrough as the default
on OSX. We don't make an equivalent attempt to prevent OS or storage
malfeasance on other Unixoid platforms --- in fact, I'd say OSX is a bit
ahead of the game in that you *can* force writethrough without
(2010/10/01 3:09), Robert Haas wrote:
2010/9/29 KaiGai Koheikai...@ak.jp.nec.com:
In addition, I want to give these entrypoints its name which
represents an appropriate purpose of the hook, rather than
a uniformed one.
It sounds like you're proposing to create a vast number of hooks
rather
A.M. wrote:
That is not correct. fsync and friends on Darwin synchronizes I/O and flushes
dirty kernel caches to the disk which meets the specification and is distinctly
different from doing nothing...
On MacOS X, fsync() always has and always will flush all file data
from host memory to the
Hi, Leonardo-san,
On Fri, Oct 1, 2010 at 4:04 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The wording should be something like CLUSTER requires transient disk
space equal to about twice the size of the table plus its indexes.
Could you merge those discussions into the final patch?
Also, please
James Robinson wrote:
Any tips / conventional wisdom regarding running postgres on
large-ish memory ccNUMA intel machines, such as a 32G dual-quad-core,
showing two NUMA nodes of 16G each? I expect each postgres backend's
non-shared memory usage to remain nice and reasonably sized,
On Fri, Oct 1, 2010 at 9:16 AM, Greg Stark st...@mit.edu wrote:
Attached is a patch to display getrusage output to EXPLAIN output.
This is the patch I mentioned previously in
http://archives.postgresql.org/pgsql-hackers/2010-02/msg00684.php and
it raises the same issues we were talking about
On Sep 30, 2010, at 9:07 PM, Itagaki Takahiro itagaki.takah...@gmail.com
wrote:
Hi, Leonardo-san,
On Fri, Oct 1, 2010 at 4:04 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The wording should be something like CLUSTER requires transient disk
space equal to about twice the size of the table plus its
On Sep 30, 2010, at 9:01 PM, KaiGai Kohei kai...@ak.jp.nec.com wrote:
(2010/10/01 3:09), Robert Haas wrote:
2010/9/29 KaiGai Koheikai...@ak.jp.nec.com:
In addition, I want to give these entrypoints its name which
represents an appropriate purpose of the hook, rather than
a uniformed one.
On Sep 29, 2010, at 10:09 AM, Alvaro Herrera alvhe...@commandprompt.com wrote:
Excerpts from Robert Haas's message of mar sep 28 10:26:54 -0400 2010:
Then:
- Begin a sequential scan with the following set of quals.
- Begin an index scan using the index called X with the following set of
Greg Smith wrote:
You didn't quote the next part of that, which says fsync() is not
sufficient to guarantee that your data is on stable
storage and on MacOS X we provide a fcntl(), called F_FULLFSYNC, to ask
the drive to flush all buffered data to stable storage. That's exactly
what turning
66 matches
Mail list logo
