Hi,
On Fri, Sep 18, 2009 at 7:34 PM, Fujii Masao wrote:
> This approach is OK if the stand-alone walreceiver is treated steadily
> by the startup process like a child process under postmaster:
>
> * Handling of some interrupts: SIGHUP, SIGTERM?, SIGINT, SIGQUIT...
> For example, the startup pro
Josh Williams wrote:
On Fri, 2009-09-18 at 09:46 -0400, Tom Lane wrote:
pet...@postgresql.org (Peter Eisentraut) writes:
Log Message:
---
Easier to translate psql help
Looks like this broke the msvc build ...
Yep, one of create_help.pl's arguments changed to not
David Do you can comment this altertatives or choices that we have?
We can support us in Bruce Schneier[1], Chief Security Technology Officer, BT
(schne...@schneier.com)
who is one of the person that knows many topics about security in the world. Is
a very nice person and allways is to able to h
On Fri, 2009-09-18 at 09:46 -0400, Tom Lane wrote:
> pet...@postgresql.org (Peter Eisentraut) writes:
> > Log Message:
> > ---
> > Easier to translate psql help
>
> Looks like this broke the msvc build ...
Yep, one of create_help.pl's arguments changed to not include the file
extension, b
On Fri, Sep 18, 2009 at 8:29 PM, Stephen Frost wrote:
> Jamie,
>
> How is the review for this coming? Do you have any thoughts regarding
> the new GUC?
>
Hi, sorry... these have been hard days... i'm just starting reviewing
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
As
Jamie,
* Robert Haas (robertmh...@gmail.com) wrote:
> Jaime Casanova
> - Largeobject access controls
How is the review for this coming? Do you have any thoughts regarding
the new GUC?
Thanks,
Stephen
signature.asc
Description: Digital signature
> "David" == "David E Wheeler" writes:
David> * I ran the following to update the SQL functions in my simple database:
David>psql -d try --set hstore_xact='--' -f hstore.sql
David>The use of `--set hstore_xact='--' was on Andrew's advice
David>via IRC, because otherwise
Folks,
Here's what came out for Mozilla, which, I hope you'll pardon my
saying so, is a teensy tad more widely used than PostgreSQL has any
plans to become.
http://www.internetnews.com/government/article.php/3839831/Mozilla+Firefox+Cleared+of+US+Export+Rules.htm
I suggest that we start by puttin
Hackers,
I'm about to launch on a program of organized alpha and beta testing by
volunteers from our community.
Initially, tests will be logged either by e-mail parsing on the
pgsql-testers mailing list, or by a web-based Radix interface if I can
get one up.
Please comment on the draft if you se
On Thu, Sep 3, 2009 at 6:47 AM, Boszormenyi Zoltan wrote:
> Boszormenyi Zoltan írta:
> >
> > Okay, we implemented only the lock_timeout GUC.
> > Patch attached, hopefully in an acceptable form.
> > Documentation included in the patch, lock_timeout
> > works the same way as statement_timeout, take
On Sep 18, 2009, at 5:18 PM, Paul Matthews wrote:
happy_birthday++;
SELECT count( happy ) FROM birthday WHERE name ~ 'Tom Lane';
WARNING : condition stack overflow: INF
Sigh,
Rob
smime.p7s
Description: S/MIME cryptographic signature
happy_birthday++;
--
Fools ignore complexity. Pragmatists suffer it.
Some can avoid it. Geniuses remove it.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Congratulations from Cuba, Tom.
I hope that you follow teaching to many of us.
Regards
"The hurry is enemy of the success: for that reason...Be patient"
Ing. Marcos L. Ortiz Valmaseda
Línea Soporte y Despliegue
Centro de Tecnologías de Almacenamiento y Análisis de Datos (CENTALAD)
Linux Use
I want to help on this area, but I need a mentor for this.
For example, Heikki will be a excellent mentor for me.
Following the theme, I think that we have to wide all questions for the process
of the acceptance of a patch on the same way that you Simon.
We could write new requirements with all
Jan Urbański napsal(a):
Petr Jelinek wrote:
So I've been working on solution with which I am happy with (does not
mean anybody else will be also though).
Hi Petr,
I'm reviewing this patch and after reading it I have some comments.
Unfortunately, when I got to the compiling part, it tu
Hello
2009/9/18 Selena Deckelmann :
> Hi!
>
> John Naylor and I reviewed this patch. John created two test cases to
> demonstrated issues described later in this email. I've attached
> those for reference.
>
> On Thu, Aug 27, 2009 at 8:04 PM, Pavel Stehule
> wrote:
>> Hello,
>>
>> this small pa
daveg wrote:
> On Fri, Sep 18, 2009 at 01:04:23PM +0200, Hans-Juergen Schoenig -- PostgreSQL
> wrote:
>> Tom,
>>
>> On behalf of the entire PostgreSQL team here in Austria I want to wish
>> you a happy birthday.
>> We hope that you fill be a vital part of PostgreSQL for many years to come.
>>
>>
On Fri, Sep 18, 2009 at 3:52 PM, Tom Lane wrote:
> Robert Haas writes:
>> The clauses are well-defined, but they don't have well-defined sides.
>> I see now what you're going for with clause_matches_join, but
>> "matches" is a pretty broad term, IMO.
>
> clause_sides_match_join?
Yes, that's perf
2009/9/19 Tom Lane :
> Should we have it throw an error if the input corresponding to a G
> symbol doesn't match the expected group separator? I'm concerned that
> that would break applications that work okay today.
>
It would be a substantial change to the behaviour, and to do it
properly we'd h
Brendan Jurd writes:
> The commitfest app has you listed as the reviewer for this patch. Any
> progress on your review?
Funny I just sent a mail to rrr explaining I don't think I'll be able to
complete my review until next Thursday. Feel free to steal me the patch
if you want to, as I'm planning
Hi Dimitri,
The commitfest app has you listed as the reviewer for this patch. Any
progress on your review?
Cheers,
BJ
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Fri, Sep 18, 2009 at 01:04:23PM +0200, Hans-Juergen Schoenig -- PostgreSQL
wrote:
> Tom,
>
> On behalf of the entire PostgreSQL team here in Austria I want to wish
> you a happy birthday.
> We hope that you fill be a vital part of PostgreSQL for many years to come.
>
> Best regards,
>
>
--On 25. August 2009 22:17:38 -0400 Alvaro Herrera
wrote:
I'm just posting in case somebody has thoughts on the UI part of it.
Other things that need fixed:
- need to figure out locking for roles; this stuff must be synchronized
with role drop
- pg_shadow and pg_roles need a join to obt
Robert Haas writes:
> The clauses are well-defined, but they don't have well-defined sides.
> I see now what you're going for with clause_matches_join, but
> "matches" is a pretty broad term, IMO.
clause_sides_match_join?
regards, tom lane
--
Sent via pgsql-hackers mail
On Fri, Sep 18, 2009 at 3:06 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Fri, Sep 18, 2009 at 1:58 PM, Tom Lane wrote:
>>> Robert Haas writes:
Mmm, I like that. Putting that bunch of hairy logic in a subroutine
instead of repeating it in several places definitely seems better. I
On Fri, 2009-09-18 at 15:43 +0300, Hannu Krosing wrote:
> >
> > * cluster - page selection made based around selecting block with
> > freespace nearest current block and we prefer keep-in-sequence to
> > avoid-contention
>
> Is the information about "current block" available to FSM search API, o
On Fri, 2009-09-18 at 16:24 +0200, Dimitri Fontaine wrote:
> Hans-Juergen Schoenig -- PostgreSQL writes:
> > Tom,
> > happy birthday.
>
> +1 from me :)
+1 from me too :D
> Regards,
> --
> dim
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services,
On Thu, 2009-09-17 at 16:26 +0100, Simon Riggs wrote:
> Just been looking again at the way FSM works. In fsm_search_avail() we
> essentially have just a single way for working out how to search the
> tree.
>
> Seems like it would be good to abstract this so that we can implement a
> number of FSM
Robert Haas writes:
> On Fri, Sep 18, 2009 at 1:58 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> Mmm, I like that. Putting that bunch of hairy logic in a subroutine
>>> instead of repeating it in several places definitely seems better. I
>>> don't really like the name "clause_matches_join", t
Herodotos Herodotou writes:
> This patch extends the query optimizer to consider joins between child tables
> when hierarchies are joined together.
I looked over this patch a bit. I am of the opinion that this is a lot
of work towards a dead-end direction :-(. The patch contains a large
amount
Pierre,
> Configurable by #define's in lwlock.c
Given that we already have dtrace/systemtap probes around the lwlocks,
is there some way you could use those instead of extra #defines?
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hacker
I have this patch, if you're interested.
LWLock Instrumentation Patch
- counts locks and waits in shared and exclusive mode
- for selected locks, measures wait and hold times
- for selected locks, displays a histogram of wait and hold times
- information is printed at backend exit
Configurable
Hi!
Below is from Brad Slinger. I'm just forwarding his message so that
the review will be in the thread for the archives. (Sorry, Brad that I
missed this earlier.. I thought you'd already replied to the list for
some reason.)
Brad says:
Please forgive my top posting. Below is my patch review.
On Fri, Sep 18, 2009 at 1:58 PM, Tom Lane wrote:
> Robert Haas writes:
>> Mmm, I like that. Putting that bunch of hairy logic in a subroutine
>> instead of repeating it in several places definitely seems better. I
>> don't really like the name "clause_matches_join", though. It's more
>> like "
Robert Haas writes:
> Mmm, I like that. Putting that bunch of hairy logic in a subroutine
> instead of repeating it in several places definitely seems better. I
> don't really like the name "clause_matches_join", though. It's more
> like "clause has well-defined sides, and mark which is which a
> Would help if I had a link, eh?
>
> http://wiki.postgresql.org/wiki/HowToBetaTest
It would also help if the mail servers cleared my original e-mail. Gr.
Here's what I posted originally, which our servers have decided to eat:
I'm about to launch on a program of organized alpha and beta t
On Sep 15, 2009, at 8:31 PM, Andrew Gierth wrote:
> Gah. rerolled to fix a missing file. includes the docs too this time.
Yay, thank you Andrew! Here are my review notes.
Testing
===
Here's what I did to try out the patch, paying special attention to in-
place upgrading:
* I built a sim
Josh Berkus wrote:
Nope, but it was on the checklist and I was being thorough.
That's a good thing. I was just seeing if I needed to get involved in
performance testing.
That would be good to have more people test the autopartitioning feature
in COPY. If you want to be involved in per
On Fri, Sep 18, 2009 at 1:26 PM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Sep 17, 2009 at 4:59 PM, Tom Lane wrote:
>>> Robert Haas writes:
You're the committer; I'm not. But I completely disagree. There
isn't any reason at all to duplicate this logic in two separate
pla
On Fri, Sep 18, 2009 at 10:31:21AM -0700, Josh Berkus wrote:
>
> > Nope, but it was on the checklist and I was being thorough.
>
> That's a good thing. I was just seeing if I needed to get involved in
> performance testing.
>
> --
> Josh Berkus
> PostgreSQL Experts Inc.
> www.pgexperts.com
I
Josh Berkus wrote:
> Bruce,
>
> >> CF17/15 to 8/14
> >> Alpha1 by 8/20
> >> CF29/15 to 10/14
> >> Alpha2 by 10/20
> >> CF311/15 to 12/14
> >> Alpha3 by 11/20
> >> CF41/15 to 2/14
> >> Alpha4 by 2/20
> >> Beta1 est. 3/1 to 3/7
> >> Release June, dep
> Please comment on the draft if you see anything I'm missing; otherwise
> I'll start the call for testers as soon as Alpha2 comes out.
Would help if I had a link, eh?
http://wiki.postgresql.org/wiki/HowToBetaTest
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make c
> Nope, but it was on the checklist and I was being thorough.
That's a good thing. I was just seeing if I needed to get involved in
performance testing.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
On Fri, Sep 18, 2009 at 10:21:08AM -0700, Josh Berkus wrote:
> On 9/17/09 3:54 PM, Greg Smith wrote:
> > On Thu, 17 Sep 2009, Dan Colish wrote:
> >
> >> - Performance appears to be the same although I don't have a good
> >> way for
> >> testing this at the moment
> >
> > Here's what I d
Robert Haas writes:
> On Thu, Sep 17, 2009 at 4:59 PM, Tom Lane wrote:
>> Robert Haas writes:
>>> You're the committer; I'm not. But I completely disagree. There
>>> isn't any reason at all to duplicate this logic in two separate
>>> places, let alone three. I'd actually be in favor of mergin
On 9/17/09 3:54 PM, Greg Smith wrote:
> On Thu, 17 Sep 2009, Dan Colish wrote:
>
>> - Performance appears to be the same although I don't have a good
>> way for
>> testing this at the moment
>
> Here's what I do to generate simple COPY performance test cases:
Is there any reason to thi
Bruce,
>> CF1 7/15 to 8/14
>> Alpha1 by 8/20
>> CF2 9/15 to 10/14
>> Alpha2 by 10/20
>> CF3 11/15 to 12/14
>> Alpha3 by 11/20
>> CF4 1/15 to 2/14
>> Alpha4 by 2/20
>> Beta1est. 3/1 to 3/7
>> Release June, depending on bugs
>
> I think that June release date is reali
On Fri, Sep 18, 2009 at 03:10:14PM +0900, Michael Paquier wrote:
> >
> > You really should be returning a value at the point since the function
> > signature defines a return type. If not the function should be void,
> > which it cannot be in this context since it is used for boolean tests
> > else
On Fri, 2009-09-18 at 11:14 -0400, Tom Lane wrote:
> Simon Riggs writes:
> > On Fri, 2009-09-18 at 07:23 -0700, Jeff Janes wrote:
> >> Is there a reason that you remove the WAL_DEBUG shown below?
>
> > WAL_DEBUG is not removed by the patch, though that section of code is
> > removed, as you obse
Jeevan Chalke writes:
> With PG84, I have tried something like this which seem incorrect to me.
> # SELECT '' AS to_number_2, to_number('-347,58', '99G999');
Well, the input doesn't actually match the format, so I'm not totally
excited about this. You do get sane results from:
regression=# se
On Fri, Sep 18, 2009 at 01:04:23PM +0200, Hans-Juergen Schoenig -- PostgreSQL
wrote:
> Tom,
>
> On behalf of the entire PostgreSQL team here in Austria I want to
> wish you a happy birthday. We hope that you fill be a vital part
> of PostgreSQL for many years to come.
Happy birthday, Tom!
Many
Simon Riggs writes:
> On Fri, 2009-09-18 at 07:23 -0700, Jeff Janes wrote:
>> Is there a reason that you remove the WAL_DEBUG shown below?
> WAL_DEBUG is not removed by the patch, though that section of code is
> removed, as you observe. I recall an earlier bug report by
> me/conversation on hack
On Fri, Sep 18, 2009 at 4:04 AM, Hans-Juergen Schoenig -- PostgreSQL
wrote:
> Tom,
>
> On behalf of the entire PostgreSQL team here in Austria I want to wish you a
> happy birthday.
> We hope that you fill be a vital part of PostgreSQL for many years to come.
In short, +1 from me.
:)
-selena
-
On Fri, 2009-09-18 at 07:23 -0700, Jeff Janes wrote:
> On Tue, Sep 15, 2009 at 2:41 PM, 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 ag
Hans-Juergen Schoenig -- PostgreSQL writes:
> Tom,
> happy birthday.
+1 from me :)
Regards,
--
dim
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Tue, Sep 15, 2009 at 2:41 PM, 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.
>
Hi Simon,
Is there a reason that you
Robert Haas writes:
> Also, stepping back from me personally, should we try to assign some
> additional reviewers to these patches? Is there some way we can
> divide up review tasks among multiple people so that we're not
> repeating each others work?
>
> Thoughts appreciated, from Heikki, Simon,
Happy nice birthday Tom Lane
On Fri, Sep 18, 2009 at 10:36 AM, Robert Haas wrote:
> On Fri, Sep 18, 2009 at 7:11 AM, A. Kretschmer
> wrote:
> > In response to Hans-Juergen Schoenig -- PostgreSQL :
> >> Tom,
> >>
> >> On behalf of the entire PostgreSQL team here in Austria I want to wish
> >> yo
pet...@postgresql.org (Peter Eisentraut) writes:
> Log Message:
> ---
> Easier to translate psql help
Looks like this broke the msvc build ...
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
On Fri, Sep 18, 2009 at 7:11 AM, A. Kretschmer
wrote:
> In response to Hans-Juergen Schoenig -- PostgreSQL :
>> Tom,
>>
>> On behalf of the entire PostgreSQL team here in Austria I want to wish
>> you a happy birthday.
>> We hope that you fill be a vital part of PostgreSQL for many years to come.
Peter Eisentraut wrote:
> On Mon, 2009-09-07 at 11:36 +0200, Magnus Hagander wrote:
> > On Mon, Sep 7, 2009 at 04:40, Itagaki
> > Takahiro wrote:
> > > There might be some places to replace it to strlcpy() instead.
> >
> > Can't comment on that without looking at the code, but it wouldn't surprise
On Fri, Sep 18, 2009 at 8:09 AM, Andrew Chernow wrote:
> Hans-Juergen Schoenig -- PostgreSQL wrote:
>>
>> Tom,
>>
>> On behalf of the entire PostgreSQL team here in Austria I want to wish you
>> a happy birthday.
>> We hope that you fill be a vital part of PostgreSQL for many years to
>> come.
>>
Happy birthday Tom, from the sunny island of Singapore. :-)
Regards,
Khee Chin.
On Fri, Sep 18, 2009 at 7:04 PM, Hans-Juergen Schoenig -- PostgreSQL
wrote:
> Tom,
>
> On behalf of the entire PostgreSQL team here in Austria I want to wish you a
> happy birthday.
> We hope that you fill be a vit
Hans-Juergen Schoenig -- PostgreSQL wrote:
Tom,
On behalf of the entire PostgreSQL team here in Austria I want to wish
you a happy birthday.
We hope that you fill be a vital part of PostgreSQL for many years to come.
Best regards,
Hans-Jürgen Schönig + team
Happy 30th Tom ;)
--
Petr Jelinek wrote:
> So I've been working on solution with which I am happy with (does not
> mean anybody else will be also though).
Hi Petr,
I'm reviewing this patch and after reading it I have some comments.
Unfortunately, when I got to the compiling part, it turned out that the
attached patch
Hans-Juergen Schoenig -- PostgreSQL wrote:
>
> Tom,
>
> On behalf of the entire PostgreSQL team here in Austria I want to wish
> you a happy birthday.
> We hope that you fill be a vital part of PostgreSQL for many years to come.
Alright, Tom ... I'm in the area, when/where's the party? ;)
In a
On Fri, 2009-09-18 at 13:04 +0200, Hans-Juergen Schoenig -- PostgreSQL
wrote:
> On behalf of the entire PostgreSQL team here in Austria I want to wish
> you a happy birthday.
> We hope that you fill be a vital part of PostgreSQL for many years to
> come.
Assuming that we have only one Tom Lane (i.
In response to Hans-Juergen Schoenig -- PostgreSQL :
> Tom,
>
> On behalf of the entire PostgreSQL team here in Austria I want to wish
> you a happy birthday.
> We hope that you fill be a vital part of PostgreSQL for many years to come.
+1
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150,
Tom,
On behalf of the entire PostgreSQL team here in Austria I want to wish
you a happy birthday.
We hope that you fill be a vital part of PostgreSQL for many years to come.
Best regards,
Hans-Jürgen Schönig + team
--
Cybertec Schoenig & Schoenig GmbH
Reyergasse 9 / 2
A-2700 Wiener
Hi,
On Thu, Sep 17, 2009 at 5:08 PM, Heikki Linnakangas
wrote:
> I'm thinking that walreceiver should be a stand-alone program that the
> startup process launches, similar to how it invokes restore_command in
> PITR recovery. Instead of using system(), though, it would use
> fork+exec, and a pipe
Fujii Masao wrote:
> Hi,
>
> On Fri, Sep 18, 2009 at 2:47 PM, Heikki Linnakangas
> wrote:
>> Heikki Linnakangas wrote:
>>> I'm thinking that walreceiver should be a stand-alone program that the
>>> startup process launches, similar to how it invokes restore_command in
>>> PITR recovery. Instead o
Hi,
On Fri, Sep 18, 2009 at 2:47 PM, Heikki Linnakangas
wrote:
> Heikki Linnakangas wrote:
>> I'm thinking that walreceiver should be a stand-alone program that the
>> startup process launches, similar to how it invokes restore_command in
>> PITR recovery. Instead of using system(), though, it wo
Hi,
With PG84, I have tried something like this which seem incorrect to me.
# SELECT '' AS to_number_2, to_number('-347,58', '99G999');
to_number_2 | to_number
-+---
| -3458
(1 row)
After browsing the code (numeric_to_number), I have found that number strin
Simon Riggs wrote:
> CTIDs don't help with optimistic locking, though it seems they can.
>
> If you don't hold open the transaction then someone else can update the
> row. That sounds good, but because of HOT it is possible that the same
> CTID with the same PK value occupies that exact CTID value
> Exactly. The application is typically going to throw a "concurrent
> update" type of error when this happens, and we don't want magic
> background operations to cause that.
>
I`d give up the possibility of using CTIDs in the way You explained
for an auto-debloater without blinking an eye. Maybe
On Fri, 2009-09-18 at 08:50 +0200, Albe Laurenz wrote:
> Tom Lane wrote:
> > > I don't see any reason why not breaking the user visible behavior of
> > > tuples CTID between any two major releases,
> >
> > > Am I completely wet here?
> >
> > Completely. This is a user-visible behavior that we h
New patch - two decimal-related memory leak fixes.
Happens on 8.4 and 8.5, maybe on older trees as well.
One of the two chunks was in the SQLDA patch originally.
This is independent from any other patches.
--
Bible has answers for everything. Proof:
"But let your communication be, Yea, yea; Nay,
Heikki Linnakangas wrote:
> Heikki Linnakangas wrote:
>> I'm thinking that walreceiver should be a stand-alone program that the
>> startup process launches, similar to how it invokes restore_command in
>> PITR recovery. Instead of using system(), though, it would use
>> fork+exec, and a pipe to com
78 matches
Mail list logo
