Heya
Just in case someone missed it on -perform and is interested, a couple
of questions have come in from VMWare, who want to use PostgreSQL as the
default reference implementation for a new TPC benchmark, TPC-V.
http://archives.postgresql.org/message-id/66ce997fb523c04e9749452273184c6c137cb
From: Robert Haas [mailto:robertmh...@gmail.com]
Sent: Friday, June 22, 2012 8:59 PM
On Fri, Jun 22, 2012 at 5:25 AM, Amit Kapila wrote:
>> Based on the discussion and suggestions in this mail chain, following
features can be implemented:
>>
>> 1. To compute the value of max LSN in data pages bas
On 28 June 2012 19:20, Andres Freund wrote:
> <0001-Add-embedded-list-interface.patch>
>
> Looks good now?
I have a few gripes.
+ * there isn't much we can test in a single linked list except that its
There are numerous references to "single linked lists", where, I
believe, "singly linked
On Tue, Jun 12, 2012 at 02:40:09PM -0400, Robert Haas wrote:
> On Tue, Jun 12, 2012 at 2:02 PM, Bruce Momjian wrote:
> > On Tue, Jun 12, 2012 at 01:50:48PM -0400, Noah Misch wrote:
> >> On Mon, Jun 11, 2012 at 05:57:41PM -0400, Alvaro Herrera wrote:
> >> > What about something like this in the roo
> On Sun, Jul 1, 2012 at 5:11 AM, Alexander Korotkov
> wrote:
>> [ new patch ]
>
> With the improved comments in pg_wchar.h, it seemed clear what needed
> to be done here, so I fixed up the MULE conversion and committed this.
> I'd appreciate it if someone would check my work, but I think it's
On Wed, Jul 4, 2012 at 9:02 AM, Joel Jacobson wrote:
> On Tue, Jul 3, 2012 at 7:49 PM, Peter Eisentraut wrote:
>>
>> I think this idea has merit. Prepare a patch and put it into the next
>> commit fest.
>
> Glad to hear, I'm on it!
>
>>
>> I see the problem that since the dump order is in genera
On Mon, Jul 2, 2012 at 3:47 PM, Robert Haas wrote:
> On Fri, Jun 29, 2012 at 3:07 AM, Bruce Momjian wrote:
>>> Personally, I'd have no problem with flat-out dropping (not demoting)
>>> both of those two specific messages. I seem to recall that Bruce has
>>> lobbied for them heavily in the past,
On Wed, Jul 4, 2012 at 3:50 AM, Albe Laurenz wrote:
> Robert Haas wrote:
>>> I can confirm that Oracle returns 0 if the third argument to
>>> INSTR is 0.
>
>> Can someone provide a suitable doc patch?
Thanks, committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Pos
On Sun, Jul 1, 2012 at 5:11 AM, Alexander Korotkov wrote:
> [ new patch ]
With the improved comments in pg_wchar.h, it seemed clear what needed
to be done here, so I fixed up the MULE conversion and committed this.
I'd appreciate it if someone would check my work, but I think it's
right.
--
Ro
2012/7/4 Robert Haas :
> On Tue, Jul 3, 2012 at 12:46 PM, Kohei KaiGai wrote:
>>> My point is that it seems like a bug that the secContext gets restored
>>> in one case and not the other, depending on which user ID was specified
>>> in SET SESSION AUTHORIZATION.
>>>
>> Sorry, the above description
On Tue, Jul 3, 2012 at 1:46 PM, Josh Kupershmidt wrote:
> On Tue, Jul 3, 2012 at 6:57 AM, Robert Haas wrote:
>> Here's a patch that attempts to begin the work of adjusting the
>> documentation for this brave new world. I am guessing that there may
>> be other places in the documentation that als
On Tue, Jul 3, 2012 at 12:46 PM, Kohei KaiGai wrote:
>> My point is that it seems like a bug that the secContext gets restored
>> in one case and not the other, depending on which user ID was specified
>> in SET SESSION AUTHORIZATION.
>>
> Sorry, the above description mention about a case when it
On Tue, Jul 3, 2012 at 11:36 PM, Amit Kapila wrote:
> Hi Shigeru/Robert,
>
>> The way fixing oid2name and pgbench seems reasonable, so applying it to
>> vacuumlo (as Peter mentioned) would be enough for this issue.
>
> Shall I consider following 2 points to update the patch:
> 1. Apply changes sim
2012/7/4 Tom Lane :
> Alvaro Herrera writes:
>> I think if you don't have a true constraint name to use here, you
>> shouldn't use anything.
>
> Yeah, I agree. Don't invent a value, just omit the field.
ok
Pavel
>
> regards, tom lane
--
Sent via pgsql-hackers mailing
Fujii Masao writes:
> waitpid() is used with "#ifdef HAVE_WAITPID" in reaper(), but NOT in
> BaseBackup().
> Why not? We can ensure that all platforms which PostgreSQL supports
> have waitpid()?
> If so, can we get rid of "#ifdef HAVE_WAITPID" in reaper()?
The Single Unix Spec V2 (1997) specifies
Alvaro Herrera writes:
> I think if you don't have a true constraint name to use here, you
> shouldn't use anything.
Yeah, I agree. Don't invent a value, just omit the field.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To mak
2012-07-04 17:25 keltezéssel, Alvaro Herrera írta:
Excerpts from Boszormenyi Zoltan's message of mié jul 04 07:03:44 -0400 2012:
2012-07-03 23:38 keltezéssel, Alvaro Herrera írta:
I don't understand why PGSemaphoreTimedLock() is not broken. I mean
surely you need a bool return to let the calle
Hi,
waitpid() is used with "#ifdef HAVE_WAITPID" in reaper(), but NOT in
BaseBackup().
Why not? We can ensure that all platforms which PostgreSQL supports
have waitpid()?
If so, can we get rid of "#ifdef HAVE_WAITPID" in reaper()?
Regards,
--
Fujii Masao
--
Sent via pgsql-hackers mailing list
I renamed the new element to DumpableObject from "proargs" to the more
general name "sortkey".
This way this element can be used by any object types in the future,
which might require sorting by additional information than type, namespace
and name.
Currently, it's only set for functions/aggregate
Excerpts from Pavel Stehule's message of mié jul 04 05:33:48 -0400 2012:
> Hello
>
> 2012/7/3 Matthew Woodcraft :
> > Peter Geoghegan writes:
> >> So I took a look at the patch eelog-2012-05-09.diff today. All of the
> >> following remarks apply to it alone.
> >
> > I've been trying out this pat
Excerpts from Boszormenyi Zoltan's message of mié jul 04 07:03:44 -0400 2012:
>
> 2012-07-03 23:38 keltezéssel, Alvaro Herrera írta:
> >
> > I don't understand why PGSemaphoreTimedLock() is not broken. I mean
> > surely you need a bool return to let the caller know whether the
> > acquisition su
Excerpts from Boszormenyi Zoltan's message of mié jul 04 06:32:46 -0400 2012:
> 2012-07-04 12:09 keltezéssel, Boszormenyi Zoltan írta:
> > You just broke initdb with this cleanup. :-)
Ouch.
> > initdb starts postgres --single, that doesn't do BackendInitialize(),
> > only PostgresMain(). So, yo
On Wed, Jul 4, 2012 at 4:21 PM, David E. Wheeler wrote:
> On Jul 4, 2012, at 9:15 AM, Magnus Hagander wrote:
>
>> Not really. We have nowhere else to recommend, since we don't run a
>> replacement for it. And we really don't want to get involved in
>> listing all the different third party sites ou
I have received positive feedback on the pg_dump --split option I suggested,
but it depends on pg_dump dumping objects in a deterministic order.
I'm committed to fixing this. The first problem I've spotted is overloaded
functions.
This patch adds a new element to DumpableObject: char *proargs
Thi
From: Robert Haas [mailto:robertmh...@gmail.com]
Sent: Tuesday, July 03, 2012 9:43 PM
On Mon, Jul 2, 2012 at 8:08 AM, Amit Kapila wrote:
>> Suggestions?
> I suggest you add this to the next CommitFest. :-)
> https://commitfest.postgresql.org/action/commitfest_view?id=14
> Meanwhile, we have t
On Jul 4, 2012, at 9:15 AM, Magnus Hagander wrote:
> Not really. We have nowhere else to recommend, since we don't run a
> replacement for it. And we really don't want to get involved in
> listing all the different third party sites out there. (For example,
> we had a reference to sourceforge.net
On Mon, Jun 11, 2012 at 5:24 PM, Fujii Masao wrote:
> On Mon, Jun 11, 2012 at 10:04 PM, Magnus Hagander wrote:
>> On Sun, Jun 10, 2012 at 4:02 PM, Fujii Masao wrote:
>>> On Sun, Jun 10, 2012 at 7:55 PM, Magnus Hagander
>>> wrote:
How about this?
>>>
>>> + /*
On Mon, Jul 2, 2012 at 8:17 PM, Fujii Masao wrote:
> On Mon, Jul 2, 2012 at 4:01 AM, Magnus Hagander wrote:
>> On Sun, Jul 1, 2012 at 7:14 PM, Fujii Masao wrote:
>>>
>>> On Fri, Jun 29, 2012 at 7:22 PM, Magnus Hagander
>>> wrote:
On Wed, Jun 27, 2012 at 7:24 PM, Fujii Masao wrote:
>
On Tue, Jul 3, 2012 at 7:49 PM, Peter Eisentraut wrote:
> I think this idea has merit. Prepare a patch and put it into the next
> commit fest.
Glad to hear, I'm on it!
> I see the problem that since the dump order is in general not
> deterministic, this will cause random reordering in your m
On 04/07/12 13:58, Asif Naeem wrote:
Patch attached. Asif, could you try a few things on a CP1252 database?
First verify if your original test case now works and then try this:
I have test the patch on Win64. postgres server is working fine now for
WIN1252. Thanks.
create function enctes
> Patch attached. Asif, could you try a few things on a CP1252 database?
First verify if your original test case now works and then try this:
>
>
I have test the patch on Win64. postgres server is working fine now for
WIN1252. Thanks.
> create function enctest() returns text as $$
> return b't
2012-07-03 23:38 keltezéssel, Alvaro Herrera írta:
I don't understand why PGSemaphoreTimedLock() is not broken. I mean
surely you need a bool return to let the caller know whether the
acquisition succeeded or failed?
Well, this is the same interface PGSemaphoreTryLock() uses.
By this reasonin
2012-07-04 12:09 keltezéssel, Boszormenyi Zoltan írta:
2012-07-03 23:31 keltezéssel, Alvaro Herrera írta:
Excerpts from Boszormenyi Zoltan's message of vie jun 29 14:30:28 -0400 2012:
Does anyone have a little time to look at the latest timeout framework
with the registration interface and the
2012-07-03 23:31 keltezéssel, Alvaro Herrera írta:
Excerpts from Boszormenyi Zoltan's message of vie jun 29 14:30:28 -0400 2012:
Does anyone have a little time to look at the latest timeout framework
with the registration interface and the 2nd patch too? I am at work
until Friday next week, aft
Hi Kaigai-san,
Sorry for delayed reply.
On Tue, Jun 26, 2012 at 10:50 PM, Kohei KaiGai wrote:
> * It seems to me expected results of the regression test is not
> attached, even though test cases were included. Please add it.
AFAICS the patch I posted contains both test script and expected res
Hello
2012/7/3 Matthew Woodcraft :
> Peter Geoghegan writes:
>> So I took a look at the patch eelog-2012-05-09.diff today. All of the
>> following remarks apply to it alone.
>
> I've been trying out this patch for my own interest (I'm very pleased to
> see work on this feature), and I have a coup
Alvaro Herrera writes:
> Applied to master, 9.2 and 9.1.
Thank you!
Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgr
Robert Haas wrote:
>> I can confirm that Oracle returns 0 if the third argument to
>> INSTR is 0.
> Can someone provide a suitable doc patch?
Here you are.
Yours,
Laurenz Albe
instr-doc.patch
Description: instr-doc.patch
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
T
On Wed, Jul 4, 2012 at 9:18 AM, Albe Laurenz wrote:
> Magnus Hagander wrote:
>> Attached are two patches, one of which I'd like to apply. Open for
>> discussion on which one.
>>
>> The smaller one, pgfoundry_1.diff, removes the suggestion to apply for
>> new projects on pgfoundry. The reason for t
Magnus Hagander wrote:
> Attached are two patches, one of which I'd like to apply. Open for
> discussion on which one.
>
> The smaller one, pgfoundry_1.diff, removes the suggestion to apply for
> new projects on pgfoundry. The reason for this being that pgfoundry
> doesn't *accept* new projects an
On Tue, Jul 3, 2012 at 9:58 PM, Bjorn Munch wrote:
> On 03/07 21.24, Magnus Hagander wrote:
>> Our documentation still refers to PostgreSQL bundled in solaris, and
>> references downloads to the pgfoundry project.
>
> Oh! I wasn't aware of that.
>
>> Attached patch removes all those references com
On Tue, Jul 3, 2012 at 10:01 PM, David E. Wheeler wrote:
> On Jul 3, 2012, at 9:20 PM, Magnus Hagander wrote:
>
>> The smaller one, pgfoundry_1.diff, removes the suggestion to apply for
>> new projects on pgfoundry. The reason for this being that pgfoundry
>> doesn't *accept* new projects anymore.
On Tue, Jul 3, 2012 at 10:32 PM, Dave Page wrote:
>
>
> On Tuesday, July 3, 2012, Peter Geoghegan wrote:
>>
>> On 3 July 2012 20:20, Magnus Hagander wrote:
>> > The second one removes the reference to pgfoundry completely. As a
>> > step in the deprecation.
>> >
>> > I'd prefer to apply the secon
Le 3 juil. 2012 à 19:53, Peter Eisentraut a écrit :
> I think it would be better if DO could be extended into some kind of
> "lambda", taking parameters and returning a value. Then you can use
> existing infrastructure for passing values and saving the return. It
> would also extend better to ot
44 matches
Mail list logo
