On Sunday 10 January 2010 01:38:07 Tom Lane wrote:
> Robert Treat writes:
> > ... I don't see much sense in worrying about it now; the 2 weeks between
> > end of CF and Beta are when we need to be cut-throat. Given that this
> > time the "must-have" feature is already in the tree, I think you will
Robert Treat writes:
> ... I don't see much sense in worrying about it now; the 2 weeks between end
> of CF and Beta are when we need to be cut-throat. Given that this time the
> "must-have" feature is already in the tree, I think you will find people
> coming
> around quickly to the side of p
On Saturday 09 January 2010 16:32:29 Robert Haas wrote:
> On Sat, Jan 9, 2010 at 4:01 PM, Peter Eisentraut wrote:
> > On lör, 2010-01-09 at 14:12 -0500, Robert Haas wrote:
> >> If we accept large patches at the very end of the development cycle,
> >> that's when people will submit them. You've pr
Andrew Dunstan writes:
> Peter Eisentraut wrote:
>> I think it would help if you could split this up into about 6 to 10
>> single-feature patches.
> ... having to handle 6 to 10 patches all hitting the same body of code
> doesn't sound terrible pleasant either.
Indeed. That sounds like rather
Magnus Hagander writes:
> On Wed, Jan 6, 2010 at 22:42, Tom Lane wrote:
>> Can't think of one, but you could try grepping for the socket-related
>> syscalls to see what variables are referenced there.
> Found two more by going over it again that way.
> Unless there are objections, I will apply
Tim Bunce writes:
> On Sat, Jan 09, 2010 at 11:16:18PM +0200, Peter Eisentraut wrote:
>> What's the reason for the temp file here?
> Defensive. If the text2macro.pl program fails/dies then you'd be left
> with a broken output file with a newer timestamp, so the next make
> wouldn't rerun text2mac
Alvaro !
My best wishes to your wife and children !
Oleg
On Sun, 10 Jan 2010, Devrim G?ND?Z wrote:
Alvaro, one of our hackers and committers and my colleague more than 4
years, had a new baby today.
Congrats Alvaro for his second daughter !
-committers, please commit your patches for our ne
2010/1/9 Devrim GÜNDÜZ :
>
> Congrats Alvaro for his second daughter !
>
+1
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
Okay *scratch head* ... if he just had a baby girl today, what was he
doing answering emails?? Priorities folks :)
Congrats Alvaro ... hopefully she came out healthy and without a trunk? :)
On Sun, 10 Jan 2010, Devrim G?ND?Z wrote:
Alvaro, one of our hackers and committers and my colleagu
Peter,
> Just to clarify: I am for sticking to the agreed dates. If some things
> are not ready by the necessary date plus/minus one, they won't make the
> release. If it's obvious earlier that something won't make the date, it
> shouldn't be committed, and maybe put on the backburner right now.
Alvaro, one of our hackers and committers and my colleague more than 4
years, had a new baby today.
Congrats Alvaro for his second daughter !
-committers, please commit your patches for our new baby elephant!
--
Devrim GÜNDÜZ, RHCE
Command Prompt - http://www.CommandPrompt.com
devrim~
On 8/01/2010 1:39 AM, Greg Sabino Mullane wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Using DBI/DBD::Pg would raise another issue - what version of libpq
would it be using? Not the one in the build being tested, that's for
sure.
Er...why not? That's what psql uses.
Because yo
Peter Eisentraut wrote:
Probably someone to actually track the open items that are mentioned
every time this discussion happens.
http://wiki.postgresql.org/wiki/Switching_PostgreSQL_from_CVS_to_Git now
has what I believe the state of the world to be in this area.
--
Greg Smith2ndQuadr
Tim Bunce wrote:
> > > Try this
> > >
> > > http://archives.postgresql.org/msgtxt.php?id=20100108124613.gl2...@timac.local
>
> That looks like it dumps the raw message. That'll cause problems for any
> messages using quoted-printable encoding. I'd hazard a guess it also
> won't do thing right th
On sön, 2010-01-10 at 00:03 +, Tim Bunce wrote:
> On Sat, Jan 09, 2010 at 11:49:22PM +, Tim Bunce wrote:
> > On Sat, Jan 09, 2010 at 11:16:18PM +0200, Peter Eisentraut wrote:
> > > On fre, 2010-01-08 at 12:46 +, Tim Bunce wrote:
> > > > *** 45,50
> > > > --- 45,55
> > > >
>
Peter Eisentraut wrote:
On fre, 2010-01-08 at 15:01 +, Tim Bunce wrote:
I didn't get any significant feedback from the earlier draft so here's
the finished 'feature patch 1' for plperl.
I think it would help if you could split this up into about 6 to 10
single-feature patches.
On Sat, Jan 09, 2010 at 11:49:22PM +, Tim Bunce wrote:
> On Sat, Jan 09, 2010 at 11:16:18PM +0200, Peter Eisentraut wrote:
> > On fre, 2010-01-08 at 12:46 +, Tim Bunce wrote:
> > > *** 45,50
> > > --- 45,55
> > >
> > > include $(top_srcdir)/src/Makefile.shlib
> > >
> > > +
On Sat, Jan 09, 2010 at 11:16:18PM +0200, Peter Eisentraut wrote:
> On fre, 2010-01-08 at 12:46 +, Tim Bunce wrote:
> > *** 45,50
> > --- 45,55
> >
> > include $(top_srcdir)/src/Makefile.shlib
> >
> > + plperl.o: perlchunks.h
> > +
> > + perlchunks.h: plc_*.pl
> > + $(P
2010/1/9 Tom Lane :
> Dean Rasheed writes:
>> I wonder if it might be better to have plpgsql_parse_dblword() ignore
>> plpgsql_LookupIdentifiers, and always do the lookups.
>
> Not if you'd like things to still work.
>
OK, I admit that I'm totally new that area of code, so I'm not seeing
it - wha
On Sat, Jan 9, 2010 at 6:20 PM, Tom Lane wrote:
> Robert Haas writes:
>> ... What I'm interested in is being
>> able to run 'git status' on a tree in which I've run a build without
>> getting a lot of extra output, and that will require ignoring all the
>> build products.
>
> I'm fairly hesitant
Robert Haas writes:
> ... What I'm interested in is being
> able to run 'git status' on a tree in which I've run a build without
> getting a lot of extra output, and that will require ignoring all the
> build products.
I'm fairly hesitant to set up ignore files that list *all* the build
products
On Sat, Jan 9, 2010 at 5:53 PM, Peter Eisentraut wrote:
> On lör, 2010-01-09 at 17:12 -0500, Robert Haas wrote:
>> Oh. Never mind. That doesn't seem useful enough to be worth spending
>> time on. What I want is to ignore all of the build products, so that
>> when I do 'git status' in my working
On lör, 2010-01-09 at 17:12 -0500, Robert Haas wrote:
> Oh. Never mind. That doesn't seem useful enough to be worth spending
> time on. What I want is to ignore all of the build products, so that
> when I do 'git status' in my working tree, I only see the the files
> I've actually added/changed.
On Sat, Jan 9, 2010 at 5:44 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Sat, Jan 9, 2010 at 5:18 PM, Andrew Dunstan wrote:
>>> Robert Haas wrote:
What I want is to ignore all of the build products
>
>>> Use a vpath build, and you'll keep those artifacts out of your source tree.
>
>> I s
On lör, 2010-01-09 at 17:19 -0500, Robert Haas wrote:
> >> Oh. Never mind. That doesn't seem useful enough to be worth spending
> >> time on. What I want is to ignore all of the build products, so that
> >> when I do 'git status' in my working tree, I only see the the files
> >> I've actually ad
Robert Haas writes:
> On Sat, Jan 9, 2010 at 5:18 PM, Andrew Dunstan wrote:
>> Robert Haas wrote:
>>> What I want is to ignore all of the build products
>> Use a vpath build, and you'll keep those artifacts out of your source tree.
> I suppose that's one answer, but of what use is it to ignore
Tim Bunce wrote:
It seems that people wanting to send in a patch have two options: send
it as text/(something) so it's readable on the archive web page but not
copy-n-paste'able because of wordwrapping, or set it as
application/octet-stream so it's downloadable but not readable on the
web page.
On Sat, Jan 09, 2010 at 02:17:27AM -0300, Alvaro Herrera wrote:
> Alvaro Herrera wrote:
> > Andrew Dunstan wrote:
> > >
> > > Tim Bunce's recent patch has been mangled apparently by the list
> > > archives. He sent it as an attachment, and that's how I have it in
> > > my mailbox, so why isn't it
On Sat, Jan 9, 2010 at 5:18 PM, Andrew Dunstan wrote:
> Robert Haas wrote:
>> On Sat, Jan 9, 2010 at 12:00 PM, Tom Lane wrote:
>>> Peter Eisentraut writes:
On fre, 2010-01-08 at 12:04 -0300, Alvaro Herrera wrote:
> Do .gitignore files have the same format as .cvsignore?
The format
Robert Haas wrote:
On Sat, Jan 9, 2010 at 12:00 PM, Tom Lane wrote:
Peter Eisentraut writes:
On fre, 2010-01-08 at 12:04 -0300, Alvaro Herrera wrote:
Do .gitignore files have the same format as .cvsignore?
The format is the same, but while cvsignore files currently
On Sat, Jan 9, 2010 at 12:00 PM, Tom Lane wrote:
> Peter Eisentraut writes:
>> On fre, 2010-01-08 at 12:04 -0300, Alvaro Herrera wrote:
>>> Do .gitignore files have the same format as .cvsignore?
>
>> The format is the same, but while cvsignore files currently list a few
>> dozen files, the propo
Alex Hunsaker writes:
> On Sat, Jan 9, 2010 at 14:06, Peter Eisentraut wrote:
>> If word of this gets out, every
>> server process on Linux will excuse itself from the OOM killer. Â And
>> then the kernel guys will add another setting to override the process
>> preference.
> ... maybe it will co
Peter Eisentraut wrote:
On fre, 2010-01-08 at 11:37 -0500, Tom Lane wrote:
Alex Hunsaker writes:
On Fri, Jan 8, 2010 at 07:27, Tom Lane wrote:
Then, somebody who wants the feature would build with, say,
-DLINUX_OOM_ADJ=0
or another value if they want that.
H
On Sat, Jan 9, 2010 at 14:06, Peter Eisentraut wrote:
> I find this whole approach a bit evil.
I would tend to agree but this type of thing has been known since about 2004...
See http://thoughts.j-davis.com/2009/11/29/linux-oom-killer/,
particularly the comment from Greg Smith.
> If word of thi
On Wed, Jan 6, 2010 at 22:42, Tom Lane wrote:
> Magnus Hagander writes:
>> Is there a good trick to find out if you've touched every place you
>> need to, because I'm very unsure I have. I don't even get a warning in
>> more than those two places, but there ought to be some way to trick
>> the sy
On Fri, Jan 08, 2010 at 10:36:43PM -0500, Robert Haas wrote:
> On Fri, Jan 8, 2010 at 10:01 AM, Tim Bunce wrote:
> > I didn't get any significant feedback from the earlier draft so here's
> > the finished 'feature patch 1' for plperl. (This builds on my earlier
> > plperl refactoring patch, and t
On Sat, Jan 9, 2010 at 4:01 PM, Peter Eisentraut wrote:
> On lör, 2010-01-09 at 14:12 -0500, Robert Haas wrote:
>> If we accept large patches at the very end of the development cycle,
>> that's when people will submit them. You've previously criticized the
>> high proportion of the release cycle
On Fri, Jan 08, 2010 at 09:47:01PM -0500, Andrew Dunstan wrote:
> Tim Bunce wrote:
> >
> >I see you've not commited it yet, so to help out I've attached
> >a new diff, over the current CVS head, with two minor changes:
> >
> >- Removed the test, as noted above.
> >- Optimized pg_verifymbstr calls t
On fre, 2010-01-08 at 12:46 +, Tim Bunce wrote:
> *** 45,50
> --- 45,55
>
> include $(top_srcdir)/src/Makefile.shlib
>
> + plperl.o: perlchunks.h
> +
> + perlchunks.h: plc_*.pl
> + $(PERL) text2macro.pl --strip='^(\#.*|\s*)$$' plc_*.pl >
> perlchunks.htmp
> + mv p
On fre, 2010-01-08 at 15:01 +, Tim Bunce wrote:
> I didn't get any significant feedback from the earlier draft so here's
> the finished 'feature patch 1' for plperl.
I think it would help if you could split this up into about 6 to 10
single-feature patches.
--
Sent via pgsql-hackers mailing
On fre, 2010-01-08 at 11:37 -0500, Tom Lane wrote:
> Alex Hunsaker writes:
> > On Fri, Jan 8, 2010 at 07:27, Tom Lane wrote:
> >> Then, somebody who wants the feature would build with, say,
> >>-DLINUX_OOM_ADJ=0
> >> or another value if they want that.
>
> > Here is a stab at that.
>
>
On lör, 2010-01-09 at 14:12 -0500, Robert Haas wrote:
> If we accept large patches at the very end of the development cycle,
> that's when people will submit them. You've previously criticized the
> high proportion of the release cycle that is set aside for CommitFest
> and beta, so I'm surprised
On Sat, Jan 09, 2010 at 12:47:00PM +0100, Magnus Hagander wrote:
> On Sat, Jan 9, 2010 at 05:54, Alvaro Herrera
> wrote:
> > Tom Lane escribió:
> >> David Fetter writes:
> >> > On Fri, Jan 08, 2010 at 10:35:24PM -0500, Tom Lane wrote:
> >> >> Probably eventually we'll be on git and this will be
2010/1/9 Tom Lane :
>> OK, I admit that I'm totally new that area of code, so I'm not seeing
>> it - what does it break?
>
> The main problem is...
Ah OK. Thanks for the explanation.
> I think that a variant of your idea could be made to work: change
> plpgsql_LookupIdentifiers to a three-state v
Dnia 2010-01-09 o godz. 20:37 Markus Wanner napisał
(a):
Hi
Joachim Wieland wrote:
Since nobody objected to the idea in general, I have implemented it.
How cool it would be if we could synchronize snapshots between the
master and the (sr) standby?
The connection poolers could use th
Dean Rasheed writes:
> 2010/1/9 Tom Lane :
>> Dean Rasheed writes:
>>> I wonder if it might be better to have plpgsql_parse_dblword() ignore
>>> plpgsql_LookupIdentifiers, and always do the lookups.
>> Not if you'd like things to still work.
> OK, I admit that I'm totally new that area of code,
Dean Rasheed writes:
> I wonder if it might be better to have plpgsql_parse_dblword() ignore
> plpgsql_LookupIdentifiers, and always do the lookups.
Not if you'd like things to still work.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
Hi
Joachim Wieland wrote:
> Since nobody objected to the idea in general, I have implemented it.
Great! I hope to get some spare cycles within the next few days to
review it.
Regards
Markus Wanner
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your s
2010/1/9 Tom Lane :
> Dean Rasheed writes:
>>> ERROR: attribute number -1 exceeds number of columns 1
>
> I guess your previous message slipped through the cracks --- sorry about
> that. It looks like the best fix is to teach ExecEvalFieldSelect that
> references to system columns are OK. Worki
Hi all!
In order to install some OS security upgrades we are going to execute
planned maintainance one the following hosts affecting the mentioned
services tomorrow (10th January 13:00-14:00 GMT). Actual expected
downtime will be a few minutes at most so this is just a heads up.
minshara.po
On Sat, Jan 9, 2010 at 9:33 AM, Peter Eisentraut wrote:
> On fre, 2010-01-08 at 21:01 -0500, Robert Haas wrote:
>> > The commitfest is a tool for people to track what is going on, not a
>> > tool to tell people what to do.
>>
>> I don't understand what you mean by this. Can you please elaborate?
Dean Rasheed writes:
>> ERROR: attribute number -1 exceeds number of columns 1
I guess your previous message slipped through the cracks --- sorry about
that. It looks like the best fix is to teach ExecEvalFieldSelect that
references to system columns are OK. Working on it now.
Magnus Hagander writes:
> On Sat, Jan 9, 2010 at 18:33, Aidan Van Dyk wrote:
>> It's already been done. It was not a lot of work (just processor time).
>> It's even already been posted to -hackers, including what the
>> differences were (i.e. which $Tags$ differed, and where, and where the
>> CV
On Sat, Jan 9, 2010 at 18:33, Aidan Van Dyk wrote:
> * Magnus Hagander [100109 12:03]:
>
>> If that's the only remaining obstacle, I'm willing to work up some
>> test scripts around that. But I'm not going to do that if it's going
>> to fall over on something else as well, because it'll be a nont
On Sat, Jan 09, 2010 at 11:55:00AM -0500, Tom Lane wrote:
> Well, I'm pretty sure that release notes are prepared off of the cvs log
> entries. I've never looked at ecpg's Changelog when working on notes,
> and I'd be prepared to bet that Bruce hasn't either. My advice is to
> drop the Changelog
* Magnus Hagander [100109 12:03]:
> If that's the only remaining obstacle, I'm willing to work up some
> test scripts around that. But I'm not going to do that if it's going
> to fall over on something else as well, because it'll be a nontrivial
> amount of work to test ir properly :-)
It's alre
On lör, 2010-01-09 at 12:00 -0500, Tom Lane wrote:
> Peter Eisentraut writes:
> > On fre, 2010-01-08 at 12:04 -0300, Alvaro Herrera wrote:
> >> Do .gitignore files have the same format as .cvsignore?
>
> > The format is the same, but while cvsignore files currently list a few
> > dozen files, the
On Sat, Jan 9, 2010 at 17:32, Tom Lane wrote:
> Magnus Hagander writes:
>> If/when we are moving the main repository, we should use the first
>> one. Yes, this will invalidate all current git clones out there, but
>> that's a one-time cost. Will there be issues? Possibly. But we're
>> *never* goi
On Sat, Jan 9, 2010 at 17:55, Tom Lane wrote:
> Michael Meskes writes:
>> On Fri, Jan 08, 2010 at 03:41:10PM +0100, Stefan Kaltenbrunner wrote:
>>> Hmm not sure I find that commit message really helpful - but is it
>>> actually of any use to maintain a Changelog file specifically for
>>> ECPG?
>
Peter Eisentraut writes:
> On fre, 2010-01-08 at 12:04 -0300, Alvaro Herrera wrote:
>> Do .gitignore files have the same format as .cvsignore?
> The format is the same, but while cvsignore files currently list a few
> dozen files, the proposed gitignore would list all files that are ever
> build
Michael Meskes writes:
> On Fri, Jan 08, 2010 at 03:41:10PM +0100, Stefan Kaltenbrunner wrote:
>> Hmm not sure I find that commit message really helpful - but is it
>> actually of any use to maintain a Changelog file specifically for
>> ECPG?
> Makes it easier to see what's new in ecpg when doing
Magnus Hagander writes:
> If/when we are moving the main repository, we should use the first
> one. Yes, this will invalidate all current git clones out there, but
> that's a one-time cost. Will there be issues? Possibly. But we're
> *never* going to get something that's *guaranteed* 100% safe, no
Does anyone know how to contact Gevik Babakhani? He has not been
responding to email, and his buildfarm member has been failing for over
6 months due to an out of date version of flex. If I don't hear from him
soon I'm going to stop it from reporting.
cheers
andrew
--
Sent via pgsql-hacker
On Sat, Jan 09, 2010 at 12:47:00PM +0100, Magnus Hagander wrote:
> But we're *never* going to get something that's *guaranteed* 100%
> safe,
You can end the sentence right there. *Everything* has a strictly
positive probability of catastrophic failure.
> not when going from something like CVS...
Robert Haas writes:
> Basically, here's my feeling. Either we have a rule that we can
> bounce large, previously-unseen patches from the final CommitFest of
> the release cycle, or we don't. If we do, then we should go ahead and
> do it, and we should do it early when it will have more effect ra
On Fri, Jan 08, 2010 at 03:41:10PM +0100, Stefan Kaltenbrunner wrote:
> Hmm not sure I find that commit message really helpful - but is it
> actually of any use to maintain a Changelog file specifically for
> ECPG?
Makes it easier to see what's new in ecpg when doing a new release. But I guess
we
On fre, 2010-01-08 at 20:03 -0800, David Fetter wrote:
> On Fri, Jan 08, 2010 at 10:35:24PM -0500, Tom Lane wrote:
> > Probably eventually we'll be on git and this will be moot, but that
> > doesn't seem to be ready to happen.
>
> What still needs to happen on this? Clearly this would be a post-8
On fre, 2010-01-08 at 12:04 -0300, Alvaro Herrera wrote:
> Do .gitignore files have the same format as .cvsignore? If that's the
> case then it's simply a matter of a "find /source -name .cvsignore
> -exec
> cp {} .gitignore \;" or similar, isn't it? Doesn't sound like
> something
> anybody shoul
On fre, 2010-01-08 at 21:01 -0500, Robert Haas wrote:
> > The commitfest is a tool for people to track what is going on, not a
> > tool to tell people what to do.
>
> I don't understand what you mean by this. Can you please elaborate?
The proposal was apparently that a small, vocal group gets to
This has broken MSVC builds - I am working on it.
cheers
andrew
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Sat, Jan 9, 2010 at 8:07 AM, Dimitri Fontaine wrote:
> Robert Haas writes:
>> I have always
>> felt that the purpose of a CommitFest was to give everyone a fair
>> shake at getting their patch reviewed, provided that they followed
>> certain ground rules.
>
> Yes, like for example submitting
Robert Haas writes:
> I have always
> felt that the purpose of a CommitFest was to give everyone a fair
> shake at getting their patch reviewed, provided that they followed
> certain ground rules.
Yes, like for example submitting the patch before the commit fest
begins.
> And I thought we had
On Sat, Jan 9, 2010 at 05:54, Alvaro Herrera wrote:
> Tom Lane escribió:
>> David Fetter writes:
>> > On Fri, Jan 08, 2010 at 10:35:24PM -0500, Tom Lane wrote:
>> >> Probably eventually we'll be on git and this will be moot, but that
>> >> doesn't seem to be ready to happen.
>>
>> > What still ne
2010/1/8 Kevin Grittner :
> Nicolas Barbier wrote:
>
>> I assume here that PG's non-SI-compatible behavior of not always
>> rollbacking any transaction that writes to a non-last version will
>> be disabled in serializable mode.
>
> Can that currently happen in PostgreSQL's snapshot isolation?!?
2009/12/4 Dean Rasheed :
> With CVS HEAD...
>
> create table foo (a int);
>
> create or replace function foo_trig_fn() returns trigger as $$
> begin
> raise notice 'In trigger: added %', new.ctid;
> return new;
> end
> $$ language plpgsql;
>
> create trigger foo_trig after insert on foo
> for ea
Hi,
Kevin Grittner wrote:
> Nicolas Barbier wrote:
>> AFAICS, detecting a "rw" dependency where the read executes after
>> the write is rather easy: the writer has created a row version
>> that is not visible to the reader's snapshot. Therefore, any time
>> a reader reads a non-last version of a
Hi Heikki,
I was recollecting our conversation that, if the index-only quals
were implemented through indexes by storing snapshots, broken data-types may
not be supported. I feel this problem might exist, if we go on design a
IOT(Index Organized Tables) / Clustered Indexes. IOT is again
77 matches
Mail list logo
