On Sun, Sep 03, 2006 at 08:30:13PM -0700, Neil Conway wrote:
> Martijn van Oosterhout said:
> > Ok, it looks like pages can be arranged hierarchically.
>
> Well, a prefix like "Todo:" is not the incantation one needs to use to
> arrange pages in hierarchies. You probably want "/" to indicate a sub
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Christopher Browne
> Sent: 04 September 2006 03:55
> To: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] gBorg status?
>
> The fact that it has been out for a week, without any public comme
On 2006-09-04, Tom Lane <[EMAIL PROTECTED]> wrote:
> OK, so if everyone is leaning to #3, the name game remains to be played.
> Do we all agree on this:
>
> "x @> y" means "x contains y"
> "x @< y" means "x is contained in y"
While I suggested something like those, I would also suggest
Tom Lane ha scritto:
OK, so if everyone is leaning to #3, the name game remains to be played.
Do we all agree on this:
"x @> y" means "x contains y"
"x @< y" means "x is contained in y"
Are we all prepared to sign a solemn oath to commit hara-kiri if we
invent a new datatype tha
On Mon, Sep 04, 2006 at 11:12:13AM +0700, Jeroen T. Vermeulen wrote:
> As I've said before, all this falls down if there is a significant cost to
> keeping one or two extra plans per prepared statement. You mentioned
> something about "tracking" plans. I don't know what that means, but it
> sound
Matteo Beccati <[EMAIL PROTECTED]> writes:
> Tom Lane ha scritto:
>> OK, so if everyone is leaning to #3, the name game remains to be played.
>> Do we all agree on this:
>>
>> "x @> y" means "x contains y"
>> "x @< y" means "x is contained in y"
>>
>> Are we all prepared to sign a solemn
> > GRANT role [, ...]
> > TO { username | GROUP groupname | PUBLIC } [, ...] [ WITH
> ADMIN
> > OPTION ]
>
> It doesn't say that anymore:
>
> http://archives.postgresql.org/pgsql-committers/2006-
> 08/msg00034.php
>
Pfft. I need to remember to check development docs as well :-) sorry
about
On Fri, 2006-08-18 at 08:52 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Thu, 2006-08-17 at 19:11 -0400, Tom Lane wrote:
> >> I noticed a minor annoyance while testing: when the system is completely
> >> idle, you get a forced segment switch every checkpoint_timeout secon
> Right now, the release notes show a list of all the significant
> items in each release, but it isn't available until the release,
> and it isn't complete (because it would be unreadable by ordinary
> users). And there is no tracking of individual items in progress
> except by individual develop
Gregory Stark <[EMAIL PROTECTED]> writes:
> Matteo Beccati <[EMAIL PROTECTED]> writes:
>
> > Tom Lane ha scritto:
> > >
> > > "x @< y" means "x is contained in y"
> >
> > ltree <@ ltree
>
> If you consider ltree entries to be sets containing all their children then
> those sound consistent.
O
Am Montag, 4. September 2006 03:57 schrieb Andrew Dunstan:
> Ah! Thanks! What had failed for me was just running with
> /path/to/old/autoconf - this one works however. Strange that a config
> package can't work out where its own installed files are.
I had that fixed in Autoconf a while back for th
Am Montag, 4. September 2006 04:06 schrieb Andrew Dunstan:
> Patch attached - seems to work on my FC5/x86_64 box. Also contains the
> OSX fix backported. Not sure that it qualifies as small though :-)
It looks pretty scary to me.
Didn't we say once that we don't want to backport fixes for platfor
Am Montag, 4. September 2006 04:10 schrieb Bruce Momjian:
> Are you saying you don't like the patch,
That's it.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
---(end of broadcast)---
TIP 4: Have you searched our list archives?
Am Montag, 4. September 2006 04:19 schrieb Bruce Momjian:
> And our email threads wander around quite a bit, with patches, ideas,
> and bugs sometimes all thrown in --- see the interval
> multiplication/division thread as a good example. How do you capture
> that?
It's easy: Those who put in the
Folks,
Because of a broken wrist, I won't be able to type much.
1. Is there any discussion being going to regrading the:
"%Allow GRANT/REVOKE permissions to be applied to all schema objects
with one command"
2. I took a brief look at gramm.y, would it be okay to create a new
section like "
On Sun, Sep 03, 2006 at 10:21:11PM -0400, Bruce Momjian wrote:
> When I tried the ecpg regression tests it complained there was no
> results/ directory. I created one and it worked.
Hmm, anyone else experiencing this? The pg_regress.sh has this code that
should create it:
outputdir="results/"
i
> > > > "x @< y" means "x is contained in y"
> > >
> > > ltree <@ ltree
> >
> > If you consider ltree entries to be sets containing all their
children
> > then those sound consistent.
Now we get to decide whether "<@" was better than the now proposed "@<"
:-)
I like <@. (or we stay clea
Am Montag, 4. September 2006 10:23 schrieb Albe Laurenz:
> This is just a 'one line' change in the documentation of
> the --with-ldap flag of ./configure
Well, if you want to link from the configure option to the place where the
feature is explained, then that should be done consistently for all
> With this approach, you still have to update your rules if
> you want to support RETURNING on your views --- but if you
> don't update them, you don't have a security hole. Basically
> the standard setup for an updatable view would use
> "ON INSERT DO INSTEAD INSERT INTO ... RETURNING
On Sep 4, 2006, at 13:12 , Tom Lane wrote:
Michael Glaesemann <[EMAIL PROTECTED]> writes:
For the record, the error I'm getting is
Makefile:3: ../../../src/Makefile.global: No such file or directory
make: *** No rule to make target `../../../src/Makefile.global'.
Stop.
From which Makefile
Hi,
Oh, I hadn't noticed that ltree spells it "<@" rather than "@<". I'd be
inclined to stick with the ltree precedent.
This was exactly my implicit proposal :)
Best regards
--
Matteo Beccati
http://phpadsnew.com
http://phppgads.com
---(end of broadcast)
Michael Meskes <[EMAIL PROTECTED]> writes:
> On Sun, Sep 03, 2006 at 10:21:11PM -0400, Bruce Momjian wrote:
>> When I tried the ecpg regression tests it complained there was no
>> results/ directory. I created one and it worked.
> Hmm, anyone else experiencing this? The pg_regress.sh has this cod
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Am Montag, 4. September 2006 04:06 schrieb Andrew Dunstan:
>> Patch attached - seems to work on my FC5/x86_64 box. Also contains the
>> OSX fix backported. Not sure that it qualifies as small though :-)
> It looks pretty scary to me.
> Didn't we say
Matteo Beccati <[EMAIL PROTECTED]> writes:
> Tom Lane ha scritto:
>> OK, so if everyone is leaning to #3, the name game remains to be played.
>> Do we all agree on this:
>>
>> "x @> y" means "x contains y"
>> "x @< y" means "x is contained in y"
> Does this mean that also contrib/ltree operators
Peter Eisentraut wrote:
> Am Montag, 4. September 2006 10:23 schrieb Albe Laurenz:
>> This is just a 'one line' change in the documentation of
>> the --with-ldap flag of ./configure
>
> Well, if you want to link from the configure option to the place where
the
> feature is explained, then that sh
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> Assuming the meaning of contains and is contained in is inclusive
> (rather than strict), then we'd have
> a <<= b : a contains b
> a =>> b : a is contained by b
I don't think we can consider that, because we already have << and >>
operators mean
i am looking at some corner case which might also cause troubles for
other people.
consider the following:
SELECT some_timestamp::date FROM very_large_table GROUP BY
some_timestamp::date
my very_large_table is around 1billion entries.
the problem is: the planner has a problem here as it is
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> On 2006-09-04, Tom Lane <[EMAIL PROTECTED]> wrote:
>> Do we all agree on this:
>>
>> "x @> y" means "x contains y"
>> "x @< y" means "x is contained in y"
> While I suggested something like those, I would also suggest that the
> existing operators
On Mon, Sep 04, 2006 at 12:06:02AM -0400, Tom Lane wrote:
> Michael Glaesemann <[EMAIL PROTECTED]> writes:
> > There's a lot of duplicate code in ecpg.
>
> No kidding :-(. The parser is bad enough but the datatype library is
> an order of magnitude worse. I don't have a great solution at hand
>
Hans-Juergen Schoenig <[EMAIL PROTECTED]> writes:
> consider the following:
> SELECT some_timestamp::date FROM very_large_table GROUP BY
> some_timestamp::date
> my very_large_table is around 1billion entries.
> the problem is: the planner has a problem here as it is taking the
> (corre
Michael Meskes <[EMAIL PROTECTED]> writes:
> On Mon, Sep 04, 2006 at 12:06:02AM -0400, Tom Lane wrote:
>> The backend utils/adt/ code gets to rely on the backend's
>> error handling and memory management protocols, which I surely do
>> not propose to remove, but how could we keep common sources whe
[EMAIL PROTECTED] (Peter Eisentraut) writes:
> sslinfo contrib module - information about current SSL certificate
> Author: Victor Wagner <[EMAIL PROTECTED]>
It was premature to add this: Bruce is still trying to get a copyright
assignment out of the author.
regards, tom l
On Sep 4, 2006, at 23:45 , Tom Lane wrote:
x >>= y "x contains y"
x >> y "x strictly contains y"
x <<= y "x is contained in y"
x << y "x is strictly contained in y"
(I'd be fine with Andrew's versions. I probably picked them up from
his ip4r code, now that I think about it.)
Michael Glaesemann <[EMAIL PROTECTED]> writes:
> [ [EMAIL PROTECTED] wrote: ]
>>> x >>= y "x contains y"
>>> x >> y "x strictly contains y"
>>> x <<= y "x is contained in y"
>>> x << y "x is strictly contained in y"
> (I'd be fine with Andrew's versions. I probably picked them up from
> hi
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Bruce Momjian wrote:
Oh, lots of grunt work. I can see that working, but at a high cost.
I doubt it. Let's just start with bugs, since that's the easy case
anyway. Our real volume is pretty low, so the cost of ma
hi tom ...
i thought about creating an index on the expression but the problem
is that this is hardly feasable.
in 8.0 (what i have here) this would block the table and i would run
out of disk space as well. this is a 600 gb biest :(
what about the planner approach?
this would solve the pro
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Uh, I have a problem with the README copyright:
> +sslinfo - information about current SSL certificate for PostgreSQL
> +==
> +Copyright (c) 2006 Cryptocom LTD
Speaking of
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Bruce Momjian wrote:
>> Without a reply from Peter, I have to assume the patch is valid.
> To make it more explicit: I think the patch is stupid, but if someone
> wants to review it, go ahead. But I am not comfortable with the "if no
> one objects,
"Jeroen T. Vermeulen" <[EMAIL PROTECTED]> writes:
> On Sun, September 3, 2006 23:52, Tom Lane wrote:
>> What exactly do you mean by "optimize away a parameter"? The way you
>> described the mechanism, there are no parameters that are "optimized
>> away", you've merely adjusted selectivity predicti
On Sat, 2006-08-26 at 22:46 -0400, Jonah H. Harris wrote:
> On 8/26/06, Alvaro Herrera <[EMAIL PROTECTED]> wrote:
> > Actually I was thinking in the design rather than the code ...
>
> Doh! We hadn't posted the design just yet. Let me write him and see
> where he's at and we'll throw something t
On Mon, Sep 04, 2006 at 17:19:37 +0200,
Hans-Juergen Schoenig <[EMAIL PROTECTED]> wrote:
>
> i thought about creating an index on the expression but the problem
> is that this is hardly feasable.
> in 8.0 (what i have here) this would block the table and i would run
That may be hard to deal
On Sep 4, 2006, at 7:04 PM, Bruno Wolff III wrote:
On Mon, Sep 04, 2006 at 17:19:37 +0200,
Hans-Juergen Schoenig <[EMAIL PROTECTED]> wrote:
i thought about creating an index on the expression but the problem
is that this is hardly feasable.
in 8.0 (what i have here) this would block the tab
Bruce Momjian <[EMAIL PROTECTED]> writes:
> This has been saved for the 8.3 release:
> http://momjian.postgresql.org/cgi-bin/pgpatches_hold
This version was withdrawn by the author for rework, no?
regards, tom lane
---(end of broadcast)--
I've gotten a little tired of reading reports that ILIKE doesn't work as
expected in UTF8. The problem is that iwchareq() in like.c is several
bricks shy of a load, as noticed e.g. here
http://archives.postgresql.org/pgsql-bugs/2005-10/msg1.php
I looked a little bit at making iwchareq less br
Tom Lane wrote:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > Bruce Momjian wrote:
> >> Without a reply from Peter, I have to assume the patch is valid.
>
> > To make it more explicit: I think the patch is stupid, but if someone
> > wants to review it, go ahead. But I am not comfortable wit
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Uh, I have a problem with the README copyright:
> > +sslinfo - information about current SSL certificate for PostgreSQL
> > +==
> > +Copyright (c) 2006 Cryptoc
Tom,
On 9/4/06, Tom Lane <[EMAIL PROTECTED]> wrote:
I propose that for ILIKE in multibyte encodings, we just pass the strings
through lower() and then use the normal LIKE code. This will be a bit
slower than what we do now, but as a wise man once said, code can be
arbitrarily fast if it needn't
Tom Lane wrote:
> [EMAIL PROTECTED] (Peter Eisentraut) writes:
> > sslinfo contrib module - information about current SSL certificate
> > Author: Victor Wagner <[EMAIL PROTECTED]>
>
> It was premature to add this: Bruce is still trying to get a
> copyright assignment out of the author.
Another one
Bruce Momjian wrote:
> How many times do I have to say this: IT IS NOT A REFACTOR PATCH AS
> REPORTED BY THE AUTHOR, AND PETER HAS NOT REFUTED THAT.
The initial patch was the feature plus some code refactoring included.
That was what the author said. I asked him to submit the refactoring
and
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Speaking of which, has anyone checked the copyrights on the other
>> proposed-for-inclusion contrib modules?
> Uh, what other ones? I see none in the patch queue.
http://archives.postgresql.org/pgsql-hackers/2006-09/msg00050.php
On Mon, Sep 04, 2006 at 19:09:16 +0200,
Hans-Juergen Schoenig <[EMAIL PROTECTED]> wrote:
>
> setting work_mem to 2gb does not help here ;)
> set it to the max value on 8.0.
> this was my first try too.
> the problem is - there is no magic switch to mislead the planner a
> little without hackin
Peter Eisentraut wrote:
> Bruce Momjian wrote:
> > How many times do I have to say this: IT IS NOT A REFACTOR PATCH AS
> > REPORTED BY THE AUTHOR, AND PETER HAS NOT REFUTED THAT.
>
> The initial patch was the feature plus some code refactoring included.
> That was what the author said. I asked
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Speaking of which, has anyone checked the copyrights on the other
> >> proposed-for-inclusion contrib modules?
>
> > Uh, what other ones? I see none in the patch queue.
>
> http://archives.postgresql.org/pgsql-h
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Speaking of which, has anyone checked the copyrights on the other
>> proposed-for-inclusion contrib modules?
> The new ISBN is the only open one. hstore hasn't had enough requests
> for inclusion.
Really? A quick search of the archi
"Guillaume Smet" <[EMAIL PROTECTED]> writes:
> On 9/4/06, Tom Lane <[EMAIL PROTECTED]> wrote:
>> I propose that for ILIKE in multibyte encodings, we just pass the strings
>> through lower() and then use the normal LIKE code.
> Perhaps it's a stupid question but what about the indexes? An index on
Bruce Momjian wrote:
> Tom Lane wrote:
>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
Speaking of which, has anyone checked the copyrights on the other
proposed-for-inclusion contrib modules?
>>> Uh, what other ones? I see none in the patch queue.
>> http://archives.pos
Tom Lane skrev:
setseed(dp)
int
- set seed for subsequent random() calls
+ set seed for subsequent random() calls (value
between -1.0 and 1.0)
Looking at the code, it would appear that the intended range is 0 to 1.
Ok.
What about the return value? The doc didn'
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Tom Lane wrote:
> >> Speaking of which, has anyone checked the copyrights on the other
> >> proposed-for-inclusion contrib modules?
>
> > The new ISBN is the only open one. hstore hasn't had enough requests
> > for inclusion.
>
> Re
Stefan Kaltenbrunner wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> >> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >>> Tom Lane wrote:
> Speaking of which, has anyone checked the copyrights on the other
> proposed-for-inclusion contrib modules?
> >>> Uh, what other ones? I see none
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
>
> setseed(dp)
> int
> - set seed for subsequent random()
> calls
> + set seed for subsequent random() calls
> (value between -1.0 and 1.0)
Looking at the code, it would appear that the intended range is 0 to 1.
Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> What about the return value? The doc didn't say anything about it.
AFAICT it's just junk. It happens to be the input times
MAX_RANDOM_VALUE, but what use is that? I wonder if we shouldn't
change the function to return VOID ... that option wasn't ava
Dhanaraj M <[EMAIL PROTECTED]> writes:
> Sorry for resubmitting this patch.
> Just now I found a problem.
> Instead of assigning initial sequence value to 1,
> I assign LLONG_MAX to avoid the buffer overflow problem.
> Please find the current version here.
This patch is a mess. In the first place
Gevik Babakhani wrote:
> Folks,
>
> Because of a broken wrist, I won't be able to type much.
>
> 1. Is there any discussion being going to regrading the:
>
> "%Allow GRANT/REVOKE permissions to be applied to all schema objects
> with one command"
No.
> 2. I took a brief look at gramm.y, w
Tom Lane wrote:
> [EMAIL PROTECTED] (Peter Eisentraut) writes:
> > sslinfo contrib module - information about current SSL certificate
> > Author: Victor Wagner <[EMAIL PROTECTED]>
>
> It was premature to add this: Bruce is still trying to get a copyright
> assignment out of the author.
I got it t
Patch has applied this patch. Thanks.
---
Peter Eisentraut wrote:
> Am Dienstag, 22. August 2006 02:52 schrieb Bruce Momjian:
> > This seems like a nice /contrib module.
> >
> > Your patch has been added to the PostgreSQL u
Patch applied. Thanks.
---
Christopher Kings-Lynne wrote:
> Hi guys,
>
> I've attached as much as I've done so far on the GIN docs. It's not a
> lot, but I'm afraid with the feature freeze in effect, I'm just not
> going
Bruce Momjian wrote:
>
> Patch has applied this patch. Thanks.
Sorry typo:
Peter has applied this patch. Thanks.
---
>
> ---
>
> Peter Eisentrau
I should have a list of open items for 8.2 within 24 hours.
--
Bruce Momjian [EMAIL PROTECTED]
EnterpriseDBhttp://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
---(end of broadcast)---
TIP 2: Don't '
On Mon, Sep 04, 2006 at 05:15:57PM +0100, Mark Cave-Ayland wrote:
> 3) Add planner support so that WITH clauses are mapped to a new type of
> node that utilises two tuplestores - an output tuplestore and a working
> tuplestore. The output tuple store will in effect be the contents of the
> table ex
Bruce Momjian wrote:
> Tom Lane wrote:
> > [EMAIL PROTECTED] (Peter Eisentraut) writes:
> > > sslinfo contrib module - information about current SSL certificate
> > > Author: Victor Wagner <[EMAIL PROTECTED]>
> >
> > It was premature to add this: Bruce is still trying to get a copyright
> > assign
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> Also, the code is released under BSD license, so why is it important if
> it says "Copyright Foo, Inc" or something else?
Because every so often we get pestered by lawyers who get worried when
there's a collection of random different copyright notices i
Alvaro Herrera wrote:
> Bruce Momjian wrote:
> > Tom Lane wrote:
> > > [EMAIL PROTECTED] (Peter Eisentraut) writes:
> > > > sslinfo contrib module - information about current SSL certificate
> > > > Author: Victor Wagner <[EMAIL PROTECTED]>
> > >
> > > It was premature to add this: Bruce is still
Tom Lane wrote:
> Michael Meskes <[EMAIL PROTECTED]> writes:
> > On Sun, Sep 03, 2006 at 10:21:11PM -0400, Bruce Momjian wrote:
> >> When I tried the ecpg regression tests it complained there was no
> >> results/ directory. I created one and it worked.
>
> > Hmm, anyone else experiencing this? Th
"Albe Laurenz" <[EMAIL PROTECTED]> writes:
> # The backend doesn't need everything that's in LIBS, however
> ! LIBS := $(filter-out -lz -lreadline -ledit -ltermcap -lncurses -lcurses
> -lldap_r $(PTHREAD_LIBS), $(LIBS))
This seems pretty risky. What if PTHREAD_LIBS contains -L switches?
They'
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > This has been saved for the 8.3 release:
> > http://momjian.postgresql.org/cgi-bin/pgpatches_hold
>
> This version was withdrawn by the author for rework, no?
Right, and the thread in patches_hold shows that. The reason it is in
Bruce Momjian wrote:
> Alvaro Herrera wrote:
>> Bruce Momjian wrote:
>>> Tom Lane wrote:
[EMAIL PROTECTED] (Peter Eisentraut) writes:
> sslinfo contrib module - information about current SSL certificate
> Author: Victor Wagner <[EMAIL PROTECTED]>
It was premature to add this: Bruc
Picking out a specific point from the thread on prepared queries:
Currently, the handling of Parse/Bind on the unnamed statement seems to
go like this:
- Parse on the unnamed statement does analysis and rewriting but does
not plan, storing the query in a special memory context dedicated to
Andrew - Supernews <[EMAIL PROTECTED]> writes:
> I believe this could usefully (and transparently to clients) be changed
> so that Bind on the unnamed statement does _not_ store the plan back in
> the unnamed statement's context, but instead produces a plan which is
> only used _for that specific p
[EMAIL PROTECTED] (Bruce Momjian) writes:
> Sequences were not being shown due to the use of lowercase 's' instead
> of 'S', and the views were not checking for table visibility with
> regards to temporary tables and sequences.
What became of my objection that the test should be on USAGE privilege
Tom Lane wrote:
> [EMAIL PROTECTED] (Bruce Momjian) writes:
> > Sequences were not being shown due to the use of lowercase 's' instead
> > of 'S', and the views were not checking for table visibility with
> > regards to temporary tables and sequences.
>
> What became of my objection that the test
Albe Laurenz wrote:
> Peter Eisentraut wrote:
> > Am Montag, 4. September 2006 10:23 schrieb Albe Laurenz:
> >> This is just a 'one line' change in the documentation of
> >> the --with-ldap flag of ./configure
> >
> > Well, if you want to link from the configure option to the place where
> the
>
Gregory Stark wrote:
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
>
> > Tom Lane wrote:
> >> Bruce Momjian <[EMAIL PROTECTED]> writes:
> >> > Patch applied. Thanks.
> >>
> >> Wait a minute. This patch changes the behavior so that
> >> LockBufferForCleanup is applied to *every* heap page, not
Peter Eisentraut wrote:
> Log Message:
> ---
> sslinfo contrib module - information about current SSL certificate
> Author: Victor Wagner <[EMAIL PROTECTED]>
This seems to have broken the bustard buildfarm member, which uses VPATH
IIRC:
make[1]: Leaving directory
`/home/andrew/bf/root/HE
Patch applied. Placed in src/tools/msvc. Thanks.
---
Magnus Hagander wrote:
> > > a.hub.org[200.46.208.251], delay=1, status=sent (250 2.7.1 Ok,
> > > discarded, id=258
> > > 35-09 - BANNED: P=p003,L=1,M=multipart/mixed
Patch applied. Thanks.
---
Gregory Stark wrote:
>
> Tom Lane <[EMAIL PROTECTED]> writes:
>
> > The reason the patch is so short is that it's a kluge. If we really
> > cared about supporting this case, more wide-ranging
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Patch applied. Thanks.
Wait a minute. This patch changes the behavior so that
LockBufferForCleanup is applied to *every* heap page, not only the ones
where there are removable tuples. It's not hard to imagine scenarios
where that results in severe sy
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Patch applied. Thanks.
>
> Wait a minute. This patch changes the behavior so that
> LockBufferForCleanup is applied to *every* heap page, not only the ones
> where there are removable tuples. It's not hard to imagine scenarios
> w
Tom Lane wrote:
> Dennis Bjorklund <[EMAIL PROTECTED]> writes:
> >
> > setseed(dp)
> > int
> > - set seed for subsequent random()
> > calls
> > + set seed for subsequent random() calls
> > (value between -1.0 and 1.0)
>
> Looking at the code, it would appear that the
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Bruce Momjian <[EMAIL PROTECTED]> writes:
>> > Patch applied. Thanks.
>>
>> Wait a minute. This patch changes the behavior so that
>> LockBufferForCleanup is applied to *every* heap page, not only the ones
>> where there are remov
"Pavel Stehule" <[EMAIL PROTECTED]> writes:
> This patch allows using any row expression in return statement and does
> transformation from untyped row to composite types if it's necessary.
This patch doesn't seem to cope with cases where the supplied tuple has
the wrong number of columns, and it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I wrote:
> Sequences were not being shown due to the use of lowercase 's' instead
> of 'S', and the views were not checking for table visibility with
> regards to temporary tables and sequences.
Tom Lane replied:
>> What became of my objection that
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> This seems to have broken the bustard buildfarm member, which uses VPATH
> IIRC:
Fixed --- I noticed it about the same time you did. I'm surprised Peter
didn't get a Makefile right the first time though ...
regards, tom lane
-
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
> Tom Lane replied:
>> What became of my objection that the test should be on USAGE privilege
>> for the containing schema instead?
> I took a stab at implementing this, but what exactly would we check? Looks
> like all the temp tables have automat
Hey Stefan, could you run some hardware diagnostics on "leveret"?
It's been returning increasingly erratic results over the past few days.
regards, tom lane
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, p
Alvaro Herrera wrote:
> > > I see the no-index case now:
> > >
> > > + if (nindexes)
> > > + LockBuffer(buf, BUFFER_LOCK_SHARE);
> > > + else
> > > + LockBufferForCleanup(buf);
> > >
> > > Let's see what Greg says, or revert.
>
Greg Sabino Mullane <[EMAIL PROTECTED]> writes:
> Attached version should now work properly.
Applied, thanks.
regards, tom lane
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Sun, Sep 03, 2006 at 12:01:06AM -0400, Tom Lane wrote:
> But ever since 7.3 the convention for identifying system objects has
> been pretty well-defined: anything that lives in one of the predefined
> schemas. What problem were you having using that approach in
> newsysviews?
It was just an is
Ühel kenal päeval, T, 2006-08-29 kell 22:12, kirjutas Joshua D. Drake:
> >> Auto creations of partitions
>
> This would be something like:
>
> create table foo () partition by ...
from the referenced MySQL manual entry
CREATE TABLE members (
...
joined DATE NOT NULL
)
PARTITION BY KEY(j
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>> This rush to apply patches just because no one seems to be capable of
>> keeping up with them not being reviewed, is starting to get a bit
>> worrisome.
> When things are placed in the patches queue, I need to get feedback if
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> SELECT *,has_schema_privilege(oid,'USAGE') FROM pg_namespace;
>> Well, if you test it as a superuser, it's going to return TRUE every
>> time.
Exactly. So I'm not seeing how we can use USAGE as a reliable test for
the case where a temporary table
1 - 100 of 124 matches
Mail list logo
