On 27/07/10 16:12, Joshua Tolley wrote:
My concern is that in a quorum system, if the quorum number is less than the
total number of replicas, there's no way to know *which* replicas composed the
quorum for any given transaction, so we can't know which servers to fail to if
the master dies.
In
Robert Haas wrote:
I have committed this patch with a few changes.
Thanks.
First, I felt that there was little point in showing this detail
only in verbose mode; indeed, it seems like that could be confusing
in some circumstances. (I thought I checked this was an index not
a
On Sun, Aug 1, 2010 at 7:11 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
In fact, it's possible for one standby to sync up to X, then disconnect and
reconnect, and have the master count it second time in the quorum.
Especially if the master doesn't notice that the standby
On Sun, Aug 1, 2010 at 12:15 AM, Pavel Stehule pavel.steh...@gmail.com wrote:
2010/8/1 Robert Haas robertmh...@gmail.com:
On Sun, Jul 25, 2010 at 11:42 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
I'm setting this as ready for committer.
Thank you very much
I took a look at this
On Sun, Aug 1, 2010 at 8:30 AM, Greg Stark gsst...@mit.edu wrote:
On Sun, Aug 1, 2010 at 7:11 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
In fact, it's possible for one standby to sync up to X, then disconnect and
reconnect, and have the master count it second time in the
On Sat, Jul 31, 2010 at 11:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Now, of the above the only cases where we'd be likely to be able to do
anything very useful with stats on the expression value are the name
case, which isn't that exciting in practice, and the tsvector cases.
For tsvector it
2010/8/1 Robert Haas robertmh...@gmail.com:
On Sun, Aug 1, 2010 at 12:15 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
2010/8/1 Robert Haas robertmh...@gmail.com:
On Sun, Jul 25, 2010 at 11:42 AM, Pavel Stehule pavel.steh...@gmail.com
wrote:
I'm setting this as ready for committer.
Pavel Stehule pavel.steh...@gmail.com writes:
so my plan
a) fix problem with ambiguous $function* like you proposed
b) fix problem with first row excepting - I can activate a detection
only for plpgsql language - I can identify LANGUAGE before.
Ick. We should absolutely NOT have a
On Sun, Aug 1, 2010 at 6:54 AM, Kevin Grittner
kevin.gritt...@wicourts.gov wrote:
Robert Haas wrote:
I have committed this patch with a few changes.
Thanks.
First, I felt that there was little point in showing this detail
only in verbose mode; indeed, it seems like that could be confusing
On Sun, Aug 1, 2010 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Pavel Stehule pavel.steh...@gmail.com writes:
so my plan
a) fix problem with ambiguous $function* like you proposed
b) fix problem with first row excepting - I can activate a detection
only for plpgsql language - I can
Alvaro Herrera alvhe...@commandprompt.com writes:
Excerpts from Tom Lane's message of sáb jul 31 09:57:13 -0400 2010:
So far as I can see, it's impossible to handle this situation when
examining only one TID per stream with no lookahead. Choosing to
advance the second stream would obviously
2010/8/1 Robert Haas robertmh...@gmail.com:
On Sun, Aug 1, 2010 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Pavel Stehule pavel.steh...@gmail.com writes:
so my plan
a) fix problem with ambiguous $function* like you proposed
b) fix problem with first row excepting - I can activate a
Tom Lane wrote:
Robert Haas writes:
I guess I'd appreciate it if someone could explain in more detail
in what cases we fail to collect stats.
[detailed description]
I don't think this can be claimed to be a corner case. If you set
up an FTS index according to the first alternative
Robert Haas robertmh...@gmail.com writes:
On Sun, Aug 1, 2010 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The need to count lines manually in function definitions is
far less than it was back when that kluge was put in.
Why?
That hack goes back to plpgsql's prehistory (it's there, though
Robert Haas robertmh...@gmail.com writes:
On Sat, Jul 31, 2010 at 11:15 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I don't think this can be claimed to be a corner case. If you set up
an FTS index according to the first alternative offered in
On Sun, Aug 1, 2010 at 11:35 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
On Sun, Aug 1, 2010 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us wrote:
The need to count lines manually in function definitions is
far less than it was back when that kluge was put in.
Currently the english parser in text search does not support multiple
words in the same position. Consider a word wikipedia.org. The text
search would return a single token wikipedia.org. However if someone
searches for wikipedia org then there will not be a match. There are
two problems here:
1.
Robert Haas robertmh...@gmail.com writes:
On Sun, Aug 1, 2010 at 11:35 AM, Tom Lane t...@sss.pgh.pa.us wrote:
Personally, rather than sweat about what the exact definition of line
numbers is, I think we should be moving further in the direction of
being able to regurgitate source text to
I wrote:
Robert Haas robertmh...@gmail.com writes:
Yeah, maybe you're right. But I'd still prefer to see us break the
ABI and do this just in 9.0 rather than changing 8.4.
OK, I can live with that. I'll take a look at it shortly.
Proposed patch attached (compiles, untested as yet).
Hello
I am sending a modified patch - changes:
a) remove special row number handling of plpgsql (first patch)
b) more robust algorithm for header rows identification
Regards
Pavel Stehule
2010/8/1 Robert Haas robertmh...@gmail.com:
On Sun, Aug 1, 2010 at 10:47 AM, Tom Lane t...@sss.pgh.pa.us
Hi Pavel,
Currently your patch isn't applying to head, from the looks of things a
function signature has changed. Can you update your patch please?
Also, having had a read through the patch itself I note that there are
no tests and no changes to documentation. Shouldn't the documentation
I tried $subject recently, and noticed some minor issues:
(1) Two warnings that suggest bugs; in src/backend/utils/adt,
datetime.c:3101:27: warning: use of logical || with constant operand;
switch to bitwise | or remove constant
And similarly for src/interfaces/ecpg/pgtypeslib/interval.c.
Neil Conway neil.con...@gmail.com writes:
I tried $subject recently, and noticed some minor issues:
(1) Two warnings that suggest bugs; in src/backend/utils/adt,
datetime.c:3101:27: warning: use of logical || with constant operand;
switch to bitwise | or remove constant
And similarly for
Neil Conway neil.con...@gmail.com writes:
*** src/backend/utils/adt/datetime.c 9 May 2010 02:15:59 - 1.212
--- src/backend/utils/adt/datetime.c 1 Aug 2010 23:09:30 -
***
*** 3098,3104
break;
On Fri, Jul 30, 2010 at 1:14 PM, Alexander Korotkov
aekorot...@gmail.com wrote:
Ok, here is the patch for multi-byte characters.
I changed arguments of levenshtein_internal function from text * to const
char * and int. I think that it makes levenshtein_internal more reusable.
For example, this
On Fri, Jul 16, 2010 at 1:19 AM, Jeff Davis pg...@j-davis.com wrote:
Thank you for the review.
On Mon, 2010-07-12 at 17:17 +0900, Itagaki Takahiro wrote:
(1) Exclusion constraints support for operators where x operator x
is false (tiny patch)
On Sun, Aug 1, 2010 at 9:30 PM, Greg Stark gsst...@mit.edu wrote:
This doesn't have to be done manually.
Agreed, if we register standbys in the master.
The streaming protocol could
include the standby sending its system id to the master. The master
could just keep a list of system ids with
On Sun, Aug 1, 2010 at 10:08 PM, Fujii Masao masao.fu...@gmail.com wrote:
On Sun, Aug 1, 2010 at 9:30 PM, Greg Stark gsst...@mit.edu wrote:
This doesn't have to be done manually.
Agreed, if we register standbys in the master.
The streaming protocol could
include the standby sending its
Neil Conway neil.con...@gmail.com writes:
I tried $subject recently, and noticed some minor issues:
I tried to duplicate your results using what I believe to be the latest
version of clang,
$ clang -v
Apple clang version 1.5 (tags/Apple/clang-60)
Target: x86_64-apple-darwin10
Thread model:
On Sun, Aug 1, 2010 at 4:53 PM, Pavel Stehule pavel.steh...@gmail.com wrote:
a) remove special row number handling of plpgsql (first patch)
Committed.
b) more robust algorithm for header rows identification
Have not gotten to this one yet.
--
Robert Haas
EnterpriseDB:
Neil Conway neil.con...@gmail.com writes:
(As an aside, is no-cpp-precomp still necessary for
reasonably-modern versions of Apple GCC?)
I looked into this point a little bit. Apple abandoned their
nonstandard precompiler as of gcc 3.3, so the switch is a no-op
in that version and later, as per
On Sun, Aug 1, 2010 at 7:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I tried to duplicate your results using what I believe to be the latest
version of clang,
I'm using SVN tip of llvm+clang from ~one week ago.
(2) clang doesn't support (or require) -no-cpp-precomp, which
src/template/darwin
On Sun, Aug 1, 2010 at 9:40 PM, Tom Lane t...@sss.pgh.pa.us wrote:
I'm still wondering about the bleats I saw for -fwrapv though.
configure already is set up to install that switch only conditionally:
# Disable optimizations that assume no overflow; needed for gcc 4.3+
33 matches
Mail list logo
