* Magnus Hagander ([EMAIL PROTECTED]) wrote:
> Stephen Frost wrote:
> > If both are made available then I think that'd work fine for us. I'm
> > concerned that the windows builds wouldn't include a version of libpq w/
> > GSSAPI...
>
> The default build wouldn't. The binary build wouldn't. If yo
To review, Pavel Stehule submitted a proposal and patch to add support
for "table functions" a few months back:
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00318.php
http://archives.postgresql.org/pgsql-patches/2007-05/msg00054.php
Pavel proposed two basically independent features:
(
On Mon, Jul 16, 2007 at 12:02:18PM -0400, Tom Lane wrote:
> No, ecpg is the only one producing warnings for me. What flex version
> do you use?
2.5.33
> What I get with flex 2.5.4 is
>
> pgc.c: In function `base_yylex':
> pgc.c:1564: warning: label `find_rule' defined but not used
> preproc.y:
On Mon, Jul 16, 2007 at 06:09:47PM +0200, Stefan Kaltenbrunner wrote:
> I think Michael is refering to:
>
> In file included from bootparse.y:380:
> bootscanner.c:1855: warning: no previous prototype for
> ‘boot_yyget_lineno’
> ...
Right, I was talking about these messages.
Michael
--
Micha
Magnus Hagander wrote:
> So what we'd need in that case is a new libpq connectionstring
> parameter. Which can be done, but it'd require that all frontends that
> use libpq add support for it - such as pgadmin. I'm not sure if the ODBC
> driver will support arbitrary arguments, otherwise that one n
Shruthi A wrote:
>> > I want to take a plan generated by the postgres optimizer and insert a
>> > constant in place of another constant in the plan. There is a function
>> > OidOutputFunctionCall( ) to get the constant. Similarly, is there any
>> > function to set the value of the constant? Also
On Tue, 17 Jul 2007, Bruce Momjian wrote:
I think the tsearch documentation is nearing completion:
http://momjian.us/expire/fulltext/HTML/textsearch.html
but I am not happy with how tsearch is enabled in a user table:
http://momjian.us/expire/fulltext/HTML/textsearch-app-tutor
Please keep the list cc'd.
Shruthi A wrote:
> On 7/17/07, Heikki Linnakangas <[EMAIL PROTECTED]> wrote:
>> Shruthi A wrote:
>> >> > I want to take a plan generated by the postgres optimizer and insert
>> a
>> >> > constant in place of another constant in the plan. There is a
>> function
>> >> > Oi
On Tue, 17 Jul 2007, Oleg Bartunov wrote:
On Tue, 17 Jul 2007, Bruce Momjian wrote:
I think the tsearch documentation is nearing completion:
http://momjian.us/expire/fulltext/HTML/textsearch.html
but I am not happy with how tsearch is enabled in a user table:
http://momjian.
> The NUM_BUFFER_PARTITIONS patch is fairly simple. We've
> noticed gains with NUM_BUFFER_PARTITIONS set between 256 and
> 2048, but little to no gain after 2048, although this might
> depend on the benchmark and platform being used. We've
Might this also be a padding issue, because 2048 part
"Jaime Casanova" <[EMAIL PROTECTED]> writes:
> http://archives.postgresql.org/pgsql-committers/2007-07/msg00142.php
> at least the part that prevents overflow and probably the one that
> reject zero in BY are clearly bugs and should be backpatched to 8.2,
> aren't they?
Well, it's a behavioral cha
Gregory Stark <[EMAIL PROTECTED]> writes:
> Was there any consensus on this change?
The implicit .so rule sucks on nearly every port, not only Linux.
We should be getting rid of the things in favor of using the much more
complete rules in Makefile.shlib.
regards, tom lane
Hi everyone,
I've been using sqlgrey for some time now and I'm very surprised by the
memory taken by the backends to which sqlgrey is connected.
look at process 4111 and 28108 . They roughly take twice the space the
other backend take.
Could there be a memory leak?
I don't know much about DBI/D
On 4/3/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
Because this patch was not completed, I have added it to the TODO list:
* Fix to_date()-related functions to consistently issue errors
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
I'm now taking another run at this is
[EMAIL PROTECTED] writes:
> I don't know much about DBI/DBD but I know sqlgrey uses a lot of
> prepare/prepare_cached statements.
Well, those aren't exactly free.
Possibly you could learn something about it by attaching to one of
these backends with gdb and executing
call MemoryContextSt
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
>> * Fix to_date()-related functions to consistently issue errors
>> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00915.php
> I'm now taking another run at this issue. Here's what I've got in mind.
This is all good but I think that self-incon
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
I think offhand that the correct semantics of the flag are "we have
redirected our original stderr into a pipe for syslogger",
We could expose syslogger's redirection_done flag, which I think has th
Stefan Kaltenbrunner napsal(a):
Zdenek Kotala wrote:
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
Stefan Kaltenbrunner wrote:
Zdenek Kotala wrote:
For sun studio -erroff=E_STATEMENT_NOT_REACHED is useful there. If you
want to determine warning tags for each warning add -errtags.
Is that
[EMAIL PROTECTED] wrote:
I don't know much about DBI/DBD but I know sqlgrey uses a lot of
prepare/prepare_cached statements.
You can inhibit DBD::Pg from using server side prepares if you need to,
by executing:
$dbh->{pg_server_prepare} = 0;
(as documented in the excellent DBD::Pg
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Yeah, that would work. You'd have to get rid of the current ad-hoc
>> method by which it is propagated to the syslogger child process
>> (EXEC_BACKEND case), because now it will have to be propagated to all
>> children; so postmaster.
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> E_FUNC_HAS_NO_RETURN_STMT is there because main is leaved by exit() instead
> return. And In another case It should be regular warning.
That should be gone now; I changed the two places that triggered it.
I'd suggest not disabling that warning.
Tom Lane wrote:
Andrew Dunstan <[EMAIL PROTECTED]> writes:
Tom Lane wrote:
Yeah, that would work. You'd have to get rid of the current ad-hoc
method by which it is propagated to the syslogger child process
(EXEC_BACKEND case), because now it will have to be propagated to all
children
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
E_FUNC_HAS_NO_RETURN_STMT is there because main is leaved by exit() instead
return. And In another case It should be regular warning.
That should be gone now; I changed the two places that triggered it.
I'd suggest not disabling tha
Zdenek Kotala <[EMAIL PROTECTED]> writes:
> Tom Lane napsal(a):
>> That should be gone now; I changed the two places that triggered it.
>> I'd suggest not disabling that warning.
> Yes I agree. Did you also clean up on old branches?
No, I'm not interested in doing that kind of fiddling on old bra
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Or, looking at it another way, why would we ever want the syslogger to
> use the chunking protocol at all?
Ah, I misunderstood you. Yeah, I think you are right: if we are
special-casing the syslogger process anyway, then it need only have
these two be
Stephen Frost wrote:
> * Magnus Hagander ([EMAIL PROTECTED]) wrote:
>> Stephen Frost wrote:
>>> If both are made available then I think that'd work fine for us. I'm
>>> concerned that the windows builds wouldn't include a version of libpq w/
>>> GSSAPI...
>> The default build wouldn't. The binary
Dave Page wrote:
> Magnus Hagander wrote:
>> So what we'd need in that case is a new libpq connectionstring
>> parameter. Which can be done, but it'd require that all frontends that
>> use libpq add support for it - such as pgadmin. I'm not sure if the ODBC
>> driver will support arbitrary argument
This is great. I've worked on 2 projects in the last year that desperately
needed this. It will certainly make the security model more seamless...
-Paul
Magnus Hagander-2 wrote:
>
> A quick status update on the SSPI authentication part of the GSSAPI
> project.
>
> I have libpq SSPI workin
I used to have a different patch from Andrew that did part of this, and
more, and conflicted rather badly with it. However, I never got around
to applying that one, and I can't seem to find it anymore.
Andrew -do you recall if you had all this in yours, and is it still
something you want in, or sh
Oleg Bartunov wrote:
> On Tue, 17 Jul 2007, Bruce Momjian wrote:
>
> > I think the tsearch documentation is nearing completion:
> >
> > http://momjian.us/expire/fulltext/HTML/textsearch.html
> >
> > but I am not happy with how tsearch is enabled in a user table:
> >
> > http://momjian.us/e
On Jul 17, 2007, at 16:24 , Bruce Momjian wrote:
I assume my_filter_name is optional right? I have updated the
prototype
to be:
tsearch([vector_column_name], [my_filter_name], text_column_name
[, ... ])
Just a style point, but would [filter_name] be better than
[my_filter_name]? You'
Michael Glaesemann wrote:
>
> On Jul 17, 2007, at 16:24 , Bruce Momjian wrote:
>
> > I assume my_filter_name is optional right? I have updated the
> > prototype
> > to be:
> >
> > tsearch([vector_column_name], [my_filter_name], text_column_name
> > [, ... ])
>
> Just a style point, but
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Simon Riggs wrote:
> We've changed the on-disk database format in 8.3, so we have an
> opportunity to change other th
Where are we on this?
---
Gregory Stark wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
>
> > I'd guess that storing 8 per page would be optimal, so each stored xid would
> > track 4,000 transactions - probably around 1
Is this item closed?
---
Alvaro Herrera wrote:
> Tom Lane wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]> writes:
> > > Tom Lane wrote:
> > >> Yeah, we had better investigate some way to clean them up. It was never
> > >> obv
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Simon Riggs wrote:
> On Fri, 2007-06-29 at 09:29 +0900, ITAGAKI Takahiro wrote:
> > Alvaro Herrera <[EMAIL PROTECTED]
This has been saved for the 8.4 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Tom Lane wrote:
> While poking at the vacuum-launcher issue currently under discussion,
> I got annoyed again at the
On 7/18/07, Tom Lane <[EMAIL PROTECTED]> wrote:
This is all good but I think that self-inconsistent format strings are
not really the main source of to_date problems. Most of the complaints
I've seen arise from to_date plowing ahead to deliver a ridiculous
answer when the input data string doesn
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Where are we on this?
Well Simon just sent the reworked patch yesterday so the answer is we haven't
started tuning this parameter. (Bruce's message is referring to the discussion
about what the optimal value of lsns per clog page would be.)
I intend
Added to TODO:
o Allow GLOBAL temporary tables to exist as empty by default in
all sessions
http://archives.postgresql.org/pgsql-hackers/2007-07/msg6.php
---
Gregory Stark wrote:
> "Pavel S
I am fighting some fires in my day job.
My pesonal TODO list for pg up to beta is:
. fix chunking muddle (see recent emails)
. complete CSV logs patch
. harden MSVC builds
I'll get to this when I can. I can dig up the patch I did if you want
it again.
cheers
andrew
Magnus Hagander wrote
Stephen Frost wrote:
-- Start of PGP signed section.
> * Tom Lane ([EMAIL PROTECTED]) wrote:
> > As of today there are two new functions exported by libpq.so since
> > 8.2 (lo_truncate and PQconnectionUsedPassword). Currently,
> > libpq/Makefile sets the major.minor shlib version to 5.1 as compare
I don't see this as applied yet.
---
Tom Lane wrote:
> "Pelle Johansson" <[EMAIL PROTECTED]> writes:
> > The age() function seem to work by first counting months until less than a
> > month remains to to the second argument,
Sorry, I see there was later discussion.
---
Tom Lane wrote:
> "Pelle Johansson" <[EMAIL PROTECTED]> writes:
> > The age() function seem to work by first counting months until less than a
> > month remains to to the second a
Bruce Momjian wrote:
>
> Is this item closed?
No, it isn't. Please add a TODO item about it:
* Prevent long-lived temp tables from causing frozen-Xid advancement
starvation
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prom
Hi,
Eecently, I have downloaded the postgresql-8.1.9.tar.gz from the official
website,and then I install in my linux System ,whose gcc version is
2.9.6.Although I can install it successfully,then result version I check is
7.2.1~£¬and how can this happen,can u tell me the reason?
Thanks a lot !
On Wed, July 18, 2007 11:07, [EMAIL PROTECTED] wrote:
> Eecently, I have downloaded the postgresql-8.1.9.tar.gz from the official
> website,and then I install in my linux System ,whose gcc version is
> 2.9.6.Although I can install it successfully,then result version I check
> is 7.2.1~£¬and how ca
[EMAIL PROTECTED] wrote:
> Eecently, I have downloaded the postgresql-8.1.9.tar.gz from the
> official website,and then I install in my linux System ,whose gcc
> version is 2.9.6.Although I can install it successfully,then result
> version I check is 7.2.1~£¬and how can this happen,can u tell me th
48 matches
Mail list logo
