Magnus Hagander mag...@hagander.net wrote:
On 15 sep 2009, at 07.21, Itagaki Takahiro itagaki.takah...@oss.ntt.co.jp
I'd like to have an opposite approach -- per-backend log files.
I can see each backend writing it, certainly, but keeping it in
separate files makes it useless without
Hi,
On Tue, Sep 15, 2009 at 2:54 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
The first thing that caught my eye is that I don't think replication
should be a real database. Rather, it should by a keyword in
pg_hba.conf, like the existing all, sameuser, samerole keywords
Yes, I did not consider that to be a problem because I did not think it
would be used on indexed tables. I figured that the gain from doing bulk
inserts into the table would be so diluted by the still-bottle-necked
index maintenance that it was OK not to use this optimization for
indexed
Does that heuristic change the timings much? If not, it seems like it
would
better to keep it simple and always do the same thing, like log the
tuples
(if it is done under one WALInsertLock, which I am assuming it is..)
It is the logging of whole pages that makes it faster.
If you fill a
Same problem. Build log attached.
...Robert
My renonc, please, try new patch. I forgot mark regproc.c file.
regards
Pavel Stehule
nm.diff.gz
Description: GNU Zip compressed data
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://llvm.org/bugs/show_bug.cgi?id=4979
will see, one issue is already fixed. I'll retry when the second one
is too.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
--
Sent via
, right now I'm not in a hurry to fix this last point.
I realize that some of the things missing make the patch uncomittable in
its current form. However, I would still appreciate a review of what I
have ready.
Regards,
Jeff Davis
generalized-index-constraints-20090915.patch.gz
On Mon, Sep 14, 2009 at 06:39:11PM +0100, Grzegorz Jaskiewicz wrote:
meanwhile, since quite a lot stuff went in over weekend, and since
Yesterday, new report at:
http://zlew.org/postgresql_static_check/scan-build-2009-09-14-1/
Looking at
On Mon, Sep 14, 2009 at 11:20:59PM -0400, Tom Lane wrote:
There is some moderately interesting reading material in section
4.17.4 Domain constraints of SQL:2008.
Not sure where to look for a copy of that, nor any particularly helpful
links :(
In particular, it appears to
me that the standard
On Tue, Sep 15, 2009 at 05:13:21AM +0100, Andrew Gierth wrote:
But there's a kicker: in Subclause 6.12, cast specification, in the
General Rules is:
a) If the cast operand specifies NULL, then the result of CS is
the null value and no further General Rules of this Subclause
Kevin Grittner wrote:
Heikki Linnakangas heikki.linnakan...@enterprisedb.com wrote:
Kevin Grittner wrote:
IMO, it would be best if the status could be sent via NOTIFY.
To where?
To registered listeners?
I guess I should have worded that as it would be best if a change is
On Wed, 2009-08-19 at 17:07 +0900, Itagaki Takahiro wrote:
Here is a WIP patch for a foreign data wrapper based dblink.
It integrates dblink module into core and adds a new functionality,
automatic transaction management. The new interface of dblink is
exported by include/foreign/dblink.h.
After playing with this a little bit, I think we need logic in the slave
to reconnect to the master if the connection is broken for some reason,
or can't be established in the first place. At the moment, that is
considered as the end of recovery, and the slave starts up. You have the
trigger file
2009/9/15 Michael Meskes mes...@postgresql.org:
Looking at
http://zlew.org/postgresql_static_check/scan-build-2009-09-14-1/report-3LPmKK.html#EndPath
it tells me that the value stored to 'counter' is never used. However, the
counter++ is called inside a loop and thus will be read the next
I was searching info about PgCluster-II yesterday and there is not much
information about it.
Do can give to me any report of this? Because I need to know the progress of
the project.
On PgFoundry, only it talks about PgCluster-1.9, but not of the 2.x versions.
Who is the PgCluster-II´s
I had the same question a while a go.
After a lot of googling I found http://www.cybertec.at/english/start_e.html
This seems to be an active replacement for the dead? pg-cluster
HTH
Regards,
Serge Fonville
On Tue, Sep 15, 2009 at 1:29 PM, Marcos Luis Ortiz Valmaseda mlor...@uci.cu
wrote:
I
Yeah, the problem here is that CyberCluster is based yet on PostgreSQL 8.1 and
is a very old version to use it.
I found the developer of PgCluster-II: Atsushi MITANI - mit...@sraw.co.jp
The hurry is enemy of the success: for that reason...Be patient
Ing. Marcos L. Ortiz Valmaseda
Línea
On Tue, Sep 15, 2009 at 5:47 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
Robert Haas wrote:
Hi, I'm reviewing this patch for the 2009-09 CommitFest.
Thank you!
It doesn't seem to compile.
Looks like the patch has bitrotted, sorry about that. Attached is an
updated
2009/9/15 Jeff Davis pg...@j-davis.com:
Attached is the latest version.
Hi Jeff,
I'm just getting started reviewing this version now. I noticed that
your patch seems to have been generated by git. Are you hosting this
work on a public repo somewhere that I can pull from? Also I think
the
2009/9/15 Jeff Davis pg...@j-davis.com:
Attached is the latest version.
The new error message for a conflict is:
ERROR: index constraint violation detected
DETAIL: tuple conflicts with existing data
How about also including the name of the constraint (or index) that
was violated? I could
On Wed, 2009-09-02 at 15:06 -0500, Kevin Grittner wrote:
Wolfgang Wilhelm wolfgang20121...@yahoo.de wrote:
if [ $# -lt 1 -o $1 = ] ] ; then
Oops. Fixed patch attached. Thanks!
The commitfest lists this as the last patch, but there was some
discussion after this. Could you/we
On Tue, Sep 15, 2009 at 1:36 AM, Peter Eisentraut pete...@gmx.net wrote:
On mån, 2009-09-14 at 21:14 -0400, Robert Haas wrote:
[P.S. I learned my lesson - last CF the equivalent email said that the
CF was closed, which of course was not what I meant at all.]
Yeah, except is it just me or is
Sam == Sam Mason s...@samason.me.uk writes:
But there's a kicker: in Subclause 6.12, cast specification, in the
General Rules is:
a) If the cast operand specifies NULL, then the result of CS is
the null value and no further General Rules of this Subclause
are applied.
That no
2009/9/15 Robert Haas robertmh...@gmail.com:
I believe the terminology we've been using, at least for the past year
since I've been involved, is as follows:
Open = open to new patches
In Progress = working on reviewing and committing patches, no longer
open to new patches
Closed = all
Andrew Gierth and...@tao11.riddles.org.uk writes:
Sam == Sam Mason s...@samason.me.uk writes:
Sam The NOT NULL constraint feels wrong as well, what are the
Sam semantics of:
Sam CREATE DOMAIN d AS INTEGER NOT NULL;
Sam SELECT a.n AS aa, b.n AS bb
Sam FROM (VALUES (CAST(1 AS
Brendan Jurd wrote:
Perhaps we should move to something like:
Accepting contributions = Under review = Complete.
I say paint the bikeshed yellow!
(h/t Dimitri)
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
On Tue, Sep 15, 2009 at 11:21:14PM +1000, Brendan Jurd wrote:
2009/9/15 Jeff Davis pg...@j-davis.com:
Attached is the latest version.
The new error message for a conflict is:
ERROR: index constraint violation detected
DETAIL: tuple conflicts with existing data
How about also
On Tue, Sep 15, 2009 at 10:08 AM, Andrew Dunstan and...@dunslane.net wrote:
Brendan Jurd wrote:
Perhaps we should move to something like:
Accepting contributions = Under review = Complete.
I say paint the bikeshed yellow!
(h/t Dimitri)
-1. Yellow bikesheds are sometimes mistaken for
On Tue, Sep 15, 2009 at 02:54:18PM +0100, Andrew Gierth wrote:
the spec _does_ appear to allow CHECK(VALUE IS NOT NULL) as a
domain constraint (in general the spec defines NOT NULL constraints
this way),
Huh, that's a trivial rewrite isn't it. Not sure why it didn't occur to
me that it's just
Scott Mohekey scott.mohe...@telogis.com wrote:
I think the issue is that we treat TIMESTAMP WITHOUT TIME ZONE as
TIMESTAMP at GMT. We then convert it to a users local timezone
within application code.
That sounds like an accident waiting to happen. Sure, you can make
it work, but you're
On Tue, Sep 15, 2009 at 09:23:09AM -0500, Kevin Grittner wrote:
Scott Mohekey scott.mohe...@telogis.com wrote:
I think the issue is that we treat TIMESTAMP WITHOUT TIME ZONE as
TIMESTAMP at GMT. We then convert it to a users local timezone
within application code.
That sounds like an
David Fetter da...@fetter.org writes:
I've looked through SQL:2008 (well, through 6WD2_02_Foundation_2007-12.pdf),
and I didn't find anything that implies that the input time zone needs
to be retrievable, nor anything that would specify the syntax for
doing so.
EXTRACT()?
On Tue, 2009-07-21 at 20:54 +0300, Alexey Klyukin wrote:
Attached is the updated version of the patch (the original description
is here: http://archives.postgresql.org/pgsql-hackers/2009-07/msg01332.php)
that doesn't use global variables.
Patch looks OK.
But for extra credit, couldn't we
Kevin == Kevin Grittner kevin.gritt...@wicourts.gov writes:
Kevin TIMESTAMP WITH TIME ZONE is not completely ANSI-compliant,
Given that the spec requires that 2009-01-31 + interval 1 month = 2009-02-31
(yes, really! see general rule 4 in subsection 6.30), I think we can safely
ignore virtually
On Tue, Sep 15, 2009 at 7:48 AM, Marcos Luis Ortiz Valmaseda mlor...@uci.cu
wrote:
Yeah, the problem here is that CyberCluster is based yet on PostgreSQL 8.1
and is a very old version to use it.
I found the developer of PgCluster-II: Atsushi MITANI - mit...@sraw.co.jp
Yeah, AFAICS,
On Tue, Sep 15, 2009 at 11:02:52AM -0400, Tom Lane wrote:
David Fetter da...@fetter.org writes:
I've looked through SQL:2008 (well, through
6WD2_02_Foundation_2007-12.pdf), and I didn't find anything that
implies that the input time zone needs to be retrievable, nor
anything that would
Peter Eisentraut pete...@gmx.net writes:
But for extra credit, couldn't we code it so that the context is set
before the PL handler is called, so that we get this functionality into
all PLs at once?
FWIW, I don't particularly agree with that --- there is no reason to
suppose that all PLs will
On Tue, 2009-09-15 at 07:29 -0400, Marcos Luis Ortiz Valmaseda wrote:
I was searching info about PgCluster-II yesterday and there is not
much information about it.
Do can give to me any report of this? Because I need to know the
progress of the project.
It is dead.
--
Devrim GÜNDÜZ, RHCE
David Fetter da...@fetter.org writes:
On Tue, Sep 15, 2009 at 11:02:52AM -0400, Tom Lane wrote:
EXTRACT()?
I see that EXTRACT() can take a time zone as input, but I don't see
anywhere that could distinguish among the following inputs, once
stored, as they have identical representations in
Hello all..
I'm using PostgreSQL 8.3..
How can I get information about the hardware utilization:
- CPU usage.
- Disk space.
- Memory allocation.
thank you.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Hi,
I saw the editor added this line:
Zoltan Boszormenyi sent in a small patch to fix a typo in an earlier
ECPG patch he sent.
This typo fix is an upstream bugfix.
Thanks.
--
Bible has answers for everything. Proof:
But let your communication be, Yea, yea; Nay, nay: for whatsoever is more
than
Andrew Gierth and...@tao11.riddles.org.uk wrote:
Kevin == Kevin Grittner kevin.gritt...@wicourts.gov
writes:
Kevin TIMESTAMP WITH TIME ZONE is not completely ANSI-compliant,
Given that the spec requires that 2009-01-31 + interval 1 month =
2009-02-31 (yes, really! see general rule 4 in
On Tue, 2009-09-15 at 22:52 +1000, Brendan Jurd wrote:
I'm just getting started reviewing this version now. I noticed that
your patch seems to have been generated by git. Are you hosting this
work on a public repo somewhere that I can pull from?
I just requested a public repo. I will publish
On Tue, 2009-09-15 at 13:16 -0300, Marc G. Fournier wrote:
Odd, I talked to him a couple of weeks ago and he was working on a
new
release in preparation for some upcoming talks he was doing ... was
working on bringing it up to support 8.3.x ...
But, I'm just prepareing new version of the
Odd, I talked to him a couple of weeks ago and he was working on a new
release in preparation for some upcoming talks he was doing ... was
working on bringing it up to support 8.3.x ...
But, I'm just prepareing new version of the PGCluster...
Mitani ... any status on this?
On Tue, 15 Sep
On Tue, 2009-09-15 at 23:21 +1000, Brendan Jurd wrote:
How about also including the name of the constraint (or index) that
was violated? I could imagine this error message being frustrating
for someone who had a table with multiple index constraints, as they
wouldn't know which one had raised
On Tue, 2009-09-15 at 08:08 -0600, Joshua Tolley wrote:
Perhaps the tuple that caused the violation as well, like UNIQUE index
violations already do? Even if we know what constraint has been tripped, we
might not know what value did it.
Or, even better, include both tuples. With these new
On Sep 15, 2009, at 8:50 AM, Tom Lane wrote:
See TIMEZONE_HOUR, TIMEZONE_MINUTE field specifications, in particular
b) Otherwise, let TZ be the interval value of the implicit
or explicit time zone associated with the datetime value
expression. If extract
On Tue, Sep 15, 2009 at 12:18 PM, Jeff Davis pg...@j-davis.com wrote:
On Tue, 2009-09-15 at 22:52 +1000, Brendan Jurd wrote:
I'm just getting started reviewing this version now. I noticed that
your patch seems to have been generated by git. Are you hosting this
work on a public repo
On Tue, Sep 15, 2009 at 5:34 AM, std pik std...@gmail.com wrote:
Hello all..
I'm using PostgreSQL 8.3..
How can I get information about the hardware utilization:
- CPU usage.
- Disk space.
- Memory allocation.
thank you.
This question would be more appropriate for
2009/9/16 Robert Haas robertmh...@gmail.com:
Instead of calling these generalized index constraints, I wonder if we
oughtn't to be calling them something like don't-overlap constraints
(that's a bad name, but something along those lines). They're not
really general at all, except compared to
On tis, 2009-09-15 at 11:32 -0400, Tom Lane wrote:
Peter Eisentraut pete...@gmx.net writes:
But for extra credit, couldn't we code it so that the context is set
before the PL handler is called, so that we get this functionality into
all PLs at once?
FWIW, I don't particularly agree with
On Tue, 2009-09-15 at 12:37 -0400, Robert Haas wrote:
Instead of calling these generalized index constraints, I wonder if we
oughtn't to be calling them something like don't-overlap constraints
(that's a bad name, but something along those lines). They're not
really general at all, except
On 9/15/09 2:34 AM, std pik wrote:
Hello all..
I'm using PostgreSQL 8.3..
How can I get information about the hardware utilization:
- CPU usage.
- Disk space.
- Memory allocation.
thank you.
This is not a question for the -hackers mailing list. Please post your
Peter Eisentraut pete...@gmx.net wrote:
The commitfest lists this as the last patch, but there was some
discussion after this. Could you/we clarify what is actually
proposed for inclusion now? I have seen proposals for:
- Linux LSB init script
- Linux non-LSB init script
- SUSE
On Tue, Sep 15, 2009 at 12:54 PM, Jeff Davis pg...@j-davis.com wrote:
On Tue, 2009-09-15 at 12:37 -0400, Robert Haas wrote:
Instead of calling these generalized index constraints, I wonder if we
oughtn't to be calling them something like don't-overlap constraints
(that's a bad name, but
2009/9/16 Robert Haas robertmh...@gmail.com:
On Tue, Sep 15, 2009 at 12:54 PM, Jeff Davis pg...@j-davis.com wrote:
I don't want to call them don't overlap constraints, because it's not
limited to a non-overlapping constraint.
Oh. What else can you do with it?
Anything that there is an
Peter Eisentraut pete...@gmx.net writes:
On tis, 2009-09-15 at 11:32 -0400, Tom Lane wrote:
FWIW, I don't particularly agree with that --- there is no reason to
suppose that all PLs will want to do this exactly the same way.
I'd imagine that we simply set the context to $language function
On Tue, Sep 15, 2009 at 1:14 PM, Brendan Jurd dire...@gmail.com wrote:
2009/9/16 Robert Haas robertmh...@gmail.com:
On Tue, Sep 15, 2009 at 12:54 PM, Jeff Davis pg...@j-davis.com wrote:
I don't want to call them don't overlap constraints, because it's not
limited to a non-overlapping
David E. Wheeler da...@kineticode.com writes:
On Sep 15, 2009, at 8:50 AM, Tom Lane wrote:
See TIMEZONE_HOUR, TIMEZONE_MINUTE field specifications, in particular
try=# select extract(timezone_hour from '2001-02-16 20:38:40 America/
Los_Angeles'::timestamptz);
You appear to be confusing what
std pik std...@gmail.com wrote:
How can I get information about the hardware utilization:
This list is for discussing development of the PostgreSQL product.
Please re-post on the novice or admin list. You'll be more likely
to get a useful reply if you give people more information, like
2009/9/16 Robert Haas robertmh...@gmail.com:
On Tue, Sep 15, 2009 at 1:14 PM, Brendan Jurd dire...@gmail.com wrote:
2009/9/16 Robert Haas robertmh...@gmail.com:
On Tue, Sep 15, 2009 at 12:54 PM, Jeff Davis pg...@j-davis.com wrote:
I don't want to call them don't overlap constraints, because
On Sep 15, 2009, at 10:17 AM, Tom Lane wrote:
try=# select extract(timezone_hour from '2001-02-16 20:38:40 America/
Los_Angeles'::timestamptz);
You appear to be confusing what PG currently does with what the spec
says.
Sorry, I thought you were referring to what PostgreSQL does. Would I
On Tue, 2009-09-15 at 13:16 -0400, Robert Haas wrote:
Uhh so what happens if I create an index constraint using the
+(integer, integer) operator?
You can use any operator that has an index search strategy. Overlaps is
probably the most useful, but you could imagine other operators, like a
On Tue, Sep 15, 2009 at 1:28 PM, Jeff Davis pg...@j-davis.com wrote:
On Tue, 2009-09-15 at 13:16 -0400, Robert Haas wrote:
Uhh so what happens if I create an index constraint using the
+(integer, integer) operator?
You can use any operator that has an index search strategy. Overlaps is
Kevin Grittner kevin.gritt...@wicourts.gov writes:
Andrew Gierth and...@tao11.riddles.org.uk wrote:
Given that the spec requires that 2009-01-31 + interval 1 month =
2009-02-31 (yes, really! see general rule 4 in subsection 6.30), I
think we can safely ignore virtually everything it says about
Kevin == Kevin Grittner kevin.gritt...@wicourts.gov writes:
Given that the spec requires that 2009-01-31 + interval 1 month =
2009-02-31 (yes, really! see general rule 4 in subsection 6.30), I
think we can safely ignore virtually everything it says about
date/time handling.
Kevin Codd
Accidentally left the doc patch out of the hstore patch posted
previously, so here it is as a separate patch.
--
Andrew (irc:RhodiumToad)
hstore-doc-20090914.patch.gz
Description: hstore doc patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your
Magnus Hagander wrote:
I'm not sure I like this as a GUC. We're going to end up with a lot of
different GUCs, and everytime we add a new log destination (admittedly
not often, of course), that increases even further. And GUCs really
don't provide the level of flexibility you'd really like to
Tom Lane wrote:
For less sane cases, I would point
out to Codd that the current calendar system was not designed by
mathematicians, and trying to superimpose strict mathematical rules on
it just leads to nonsense (like the spec's requirements).
He's not listening
Jeff Davis pg...@j-davis.com writes:
On Tue, 2009-09-15 at 13:16 -0400, Robert Haas wrote:
Uhh so what happens if I create an index constraint using the
+(integer, integer) operator?
You can use any operator that has an index search strategy. Overlaps is
probably the most useful, but you
Tom Lane t...@sss.pgh.pa.us wrote:
[ shrug... ] We *have* that property, for sane cases such as
adding and subtracting a fixed number of days.
Adding and subtracting months is very common in business software.
I have seen application bugs related to this many times. I suspect
that such
On Tue, 2009-09-15 at 13:48 -0400, Robert Haas wrote:
So it allows us to create constraints of the following form?
For all A in the index, there exists no B in the index such that the
given operator (which must be a binary operator returning boolean)
holds of A and B.
Yes. And it's slightly
On Tue, Sep 15, 2009 at 11:31:48AM -0700, Jeff Davis wrote:
On Tue, 2009-09-15 at 13:48 -0400, Robert Haas wrote:
So it allows us to create constraints of the following form?
For all A in the index, there exists no B in the index such that the
given operator (which must be a binary
S1, S2 are concurrent sessions:
S1: create table test_par (v int);
S1: create table test_ch1 (check (v 0 and v = 2)) inherits (test_par);
S1: create table test_ch2 (check (v 2 and v = 4)) inherits (test_par);
S1: begin;
S1: drop table test_ch1 cascade;
S2: select * from test_par where v = 3;
On Tue, Sep 15, 2009 at 3:03 PM, David Fetter da...@fetter.org wrote:
* operator-based constraints
A little math-ier, but talks about the API rather than details of
the server implementation.
Or operator-exclusion constraints? Operator-based exclusion constraints?
I'm feeling
Andrew Gierth and...@tao11.riddles.org.uk wrote:
(To me, the fact that the spec's idea of 2009-01-31 + 1 month
corresponds to a value that current_date will never be equal to is
a far greater show-stopper.)
You get to pick which way you want to normalize that to the calendar
-- 31 days past
On Tue, 2009-09-15 at 14:49 -0400, Tom Lane wrote:
Does it behave sanely for operators that are non-commutative, such
as ''? (I'm not even very sure that I know what sanely would be
in such a case.)
One of the requirements is commutativity (I called it symmetry in the
docs, for some reason, I
On Tue, 2009-09-15 at 12:03 -0700, David Fetter wrote:
Interesting :) I take it op1..opN (it's opN, not op2, right?) need to
commute?
Yeah, it's opN.
And they should commute, but my current patch won't stop you. I think I
should stop that though, it's pretty difficult to think of a good
Jeff Davis pg...@j-davis.com writes:
On Tue, 2009-09-15 at 14:49 -0400, Tom Lane wrote:
Does it behave sanely for operators that are non-commutative, such
as ''? (I'm not even very sure that I know what sanely would be
in such a case.)
If you try it, my current patch won't stop you. Maybe I
On Tue, Sep 15, 2009 at 12:22:46PM -0700, Jeff Davis wrote:
On Tue, 2009-09-15 at 12:03 -0700, David Fetter wrote:
* operator-based constraints
A little math-ier, but talks about the API rather than details of
the server implementation.
I like this much better. Maybe index
On Sep 15, 2009, at 11:01 AM, Andrew Gierth wrote:
If you want to store both a timestamp and an associated timezone you
can do
it right now, using a composite type or two columns, with the
advantage that
you get semantics that you can rely on.
How would a composite work in practice? Can
Since our shop seems to use domains more than most, I figured I
should comment on this thread.
Sam Mason s...@samason.me.uk wrote:
On Tue, Sep 15, 2009 at 02:54:18PM +0100, Andrew Gierth wrote:
and the wording from 6.12 implies that that check is still
skipped in the case of NULLs (so that
Jeff Davis pg...@j-davis.com writes:
S1, S2 are concurrent sessions:
S1: create table test_par (v int);
S1: create table test_ch1 (check (v 0 and v = 2)) inherits (test_par);
S1: create table test_ch2 (check (v 2 and v = 4)) inherits (test_par);
S1: begin;
S1: drop table test_ch1 cascade;
On Tue, 2009-09-15 at 16:58 -0400, Tom Lane wrote:
Oh? Are you using 8.4+?
Oops, connecting to the wrong port. 8.5-dev works fine.
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
Best Regards,
Ed Koch
Principal
Addison Search
212-378-1634
1350 Broadway NY,NY suite 810, 10018
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate,
Perhaps you should post to the correct mailing list, which is
pgsql-j...@postgresql.org. Posting a real description of the position
- including where it's located, what the responsibilities are, and so
on, would be a good idea too.
...Robert
--
Sent via pgsql-hackers mailing list
On Tue, 2009-09-15 at 12:49 -0700, David Fetter wrote:
I like this much better. Maybe index operator constraints or operator
index constraints?
The word, index goes to implementation details, which may change.
Ok, let's vote on a name then:
operator constraints
operator exclusion
On Tue, 2009-09-15 at 14:42 -0700, Jeff Davis wrote:
operator constraints
operator exclusion constraints
operator conflict constraints
conflict operator constraints
operator index constraints
index constraints
generalized index constraints
something else?
Just to add a couple more
Jeff Davis pg...@j-davis.com writes:
On Tue, 2009-09-15 at 14:42 -0700, Jeff Davis wrote:
operator constraints
operator exclusion constraints
operator conflict constraints
conflict operator constraints
operator index constraints
index constraints
generalized index constraints
something
On Tue, Sep 15, 2009 at 10:41:59PM +0100, Simon Riggs wrote:
OK, here is the latest version of the Hot Standby patchset. This is
about version 30+ by now, but we should regard this as 0.2.1 Patch
against CVS HEAD (now): clean apply, compile, no known bugs.
Kudos
Cheers,
David.
--
On Tue, Sep 15, 2009 at 05:52:35PM -0400, Tom Lane wrote:
Jeff Davis pg...@j-davis.com writes:
On Tue, 2009-09-15 at 14:42 -0700, Jeff Davis wrote:
operator constraints
operator exclusion constraints
operator conflict constraints
conflict operator constraints
operator index
On Wed, Sep 16, 2009 at 2:23 AM, Kevin Grittner kevin.gritt...@wicourts.gov
wrote:
Scott Mohekey scott.mohe...@telogis.com wrote:
I think the issue is that we treat TIMESTAMP WITHOUT TIME ZONE as
TIMESTAMP at GMT. We then convert it to a users local timezone
within application code.
Robert Haas robertmh...@gmail.com writes:
Here we go again. Following Tom's advice to not insert crocks in
add_path(), I've instead introduced a noopjoin path type which ignores
its inner side. This could possibly be simplified to just a noop
path that doesn't even include an outer side, but
Joe, Itagaki,
Can you provide an update on this patch? Joe, you were going to
review and possibly commit it. Itagaki, did you have a new version?
Are there any outstanding issues?
Thanks,
Stephen
signature.asc
Description: Digital signature
Michael,
I just wanted to follow-up on your pgbench patch. The latest version
that I see is from August 13th. Is that the correct patch to be
reviewing? Do you have any other updates on it?
Thanks!
Stephen
signature.asc
Description: Digital signature
Mark,
Your last email on this patch, from August 9th, indicates that you've
still got TODO: redo pg_stat_lock_waits Has you updated this
patch since then?
Thanks!
Stephen
signature.asc
Description: Digital signature
Hi,
2009/9/16 Marc G. Fournier scra...@hub.org:
Odd, I talked to him a couple of weeks ago and he was working on a new
release in preparation for some upcoming talks he was doing ... was working
on bringing it up to support 8.3.x ...
Yes. He will make a presentation about PGCluster at PGCon
On Tue, Sep 15, 2009 at 9:29 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
Here we go again. Following Tom's advice to not insert crocks in
add_path(), I've instead introduced a noopjoin path type which ignores
its inner side. This could possibly be
On Tue, Sep 15, 2009 at 10:10 PM, Robert Haas robertmh...@gmail.com wrote:
* I'm not sure about this, because surely you would have tested it,
but isn't it looking at the wrong side of the join clauses? I thought
the idea is to prove the nullable (inner) side of the join unique.
Grr. I
1 - 100 of 112 matches
Mail list logo
