Tom Lane wrote:
> The point here is really that we keep finding reasons to, if not
> flat-out change the interface to PLs, at least expand their
> responsibilities. Not to push it too hard, but we still have only
> one PL with a validator procedure, which IIRC was your own addition
> to that API.
"Neil Conway" <[EMAIL PROTECTED]> writes
> PostgreSQL should invalidate a cached query plan when one of the objects
> the plan depends upon is modified.
It just comes into my mind that current cache invalidation implementation
may need to consider the future query result cache.
The question comes
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Also, since plPerlNG is maintained on PgFoundry, are the changes you are
> making to core getting migrated back to the main project itself?
I don't know, and not being a maintainer of the pgfoundry project,
it is *definitely* not my problem. But I
One key point to note here is Joshua already saying they wish, like
plPerl, to continue maintaining the "core code" outside of the core
distribution ... the way I read that is they just want to be 'in core' to
piggy back on the distribution, not to make development/maintenance any
easier ...
I
On Sat, 2 Apr 2005, Peter Eisentraut wrote:
I'm not convinced that PLs are more tied to the core than say OpenFTS,
and if we can't maintain that kind of thing externally, then this whole
extension thing sounds like a failure to me.
As many times as Peter and I butt heads, on this I have to agree
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I'm not convinced that PLs are more tied to the core than say OpenFTS,
> and if we can't maintain that kind of thing externally, then this whole
> extension thing sounds like a failure to me.
It's *possible* to do it. Whether it's a net savings of
Joshua D. Drake wrote:
> We at Command Prompt are in the process of completing
> a new rev of plPHP. The new rev will not require the
> PHP source. It will only require that PHP is installed.
How can that be?
> Are we interested in having plPHP in core?
Personally, I'm not too excited about it.
Tom Lane wrote:
> PLs are sufficiently tightly tied to the core that it's probably
> easier to maintain them as part of our core CVS than otherwise.
> (Ask Joe Conway about PL/R.
As a matter of fact, let's ask him.
> Thomas Hallgren is probably not that
> happy about maintaining pl/java out of c
Marc G. Fournier wrote:
On Fri, 1 Apr 2005, Joshua D. Drake wrote:
Hello,
We at Command Prompt are in the process of completing
a new rev of plPHP. The new rev will not require the
PHP source. It will only require that PHP is installed.
In other words it can be installed just like any other pl
lang
Alvaro Herrera wrote:
On Fri, Apr 01, 2005 at 07:11:14PM -0800, Joshua D. Drake wrote:
Hi Joshua,
We at Command Prompt are in the process of completing
a new rev of plPHP. The new rev will not require the
PHP source. It will only require that PHP is installed.
In other words it can be installed
I'm thinking that a pl/PHP is much more interesting for the long term
than, say, pl/tcl (mind you, I am a Tcl partisan from way back, but
I see that many people are not so enlightened). Barring any licensing
problems I think this is something to pursue.
Per the license issue it is licensed und
> In other words it can be installed just like any other pl
> language.
>
> Are we interested in having plPHP in core?
>
Yes , it must come into the core as PHP developers would now get
tempted to write functions inside database this would cut out
adoption of Databases which do not have PHP ty
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> On Fri, 1 Apr 2005, Joshua D. Drake wrote:
>> Are we interested in having plPHP in core?
> Is there a reason why it can no longer operate as a standalone language
> out of pgfoundry, like pl/java and pl/perl?
PLs are sufficiently tightly tied to t
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
>> Does anyone know why so many LEFT JOINs are used in psql/describe.c to
>> join to the pg_namespace table, like here:
> Yes, pg_relnamespace is definitely not null. I've actually already removed
> the left joins from my \df patch, since I had to
On Fri, 1 Apr 2005, Joshua D. Drake wrote:
Hello,
We at Command Prompt are in the process of completing
a new rev of plPHP. The new rev will not require the
PHP source. It will only require that PHP is installed.
In other words it can be installed just like any other pl
language.
Are we interested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Does anyone know why so many LEFT JOINs are used in psql/describe.c to
> join to the pg_namespace table, like here:
>
> I thought a pg_class row always pointed to a valid pg_namespace row
> because of our dependency restrictions.
Yes, pg_relnamesp
On Fri, Apr 01, 2005 at 07:11:14PM -0800, Joshua D. Drake wrote:
Hi Joshua,
> We at Command Prompt are in the process of completing
> a new rev of plPHP. The new rev will not require the
> PHP source. It will only require that PHP is installed.
>
> In other words it can be installed just like an
Joshua D. Drake wrote:
> Hello,
>
> We at Command Prompt are in the process of completing
> a new rev of plPHP. The new rev will not require the
> PHP source. It will only require that PHP is installed.
>
> In other words it can be installed just like any other pl
> language.
>
> Are we interest
Does anyone know why so many LEFT JOINs are used in psql/describe.c to
join to the pg_namespace table, like here:
printfPQExpBuffer(&buf,
"SELECT c.oid,\n"
" n.nspname,\n"
" c.relname\n"
"FROM pg_catalog.pg_class c\n"
" LEFT JOIN pg_catalog.pg_namespace n ON
Hello,
We at Command Prompt are in the process of completing
a new rev of plPHP. The new rev will not require the
PHP source. It will only require that PHP is installed.
In other words it can be installed just like any other pl
language.
Are we interested in having plPHP in core?
Sincerely,
Joshua
"Eric B. Ridge" <[EMAIL PROTECTED]> writes:
> The tuplestore stuff sounds like the right solution, but in the
> interests of providing a quick patch to my production environment does
> it makes sense to make a copy of the SPI_tuptable during the first-call
> of the SRF (allocated in the SRF's me
On Apr 1, 2005, at 3:55 PM, Tom Lane wrote:
"Eric B.Ridge" <[EMAIL PROTECTED]> writes:
Like I said, everything
usually works without problems, but from time to time it crashes.
If you rebuild with --enable-cassert, does the crash get more
reproducible?
Indeed. Every time. This is now the default
"Eric B.Ridge" <[EMAIL PROTECTED]> writes:
> Like I said, everything
> usually works without problems, but from time to time it crashes.
If you rebuild with --enable-cassert, does the crash get more
reproducible? (Personally I would never consider developing any
backend C code without that tur
>> -Original Message-
>> From: Marian POPESCU [mailto:[EMAIL PROTECTED]
>> Sent: Friday, April 01, 2005 8:06 AM
>> To: pgsql-hackers@postgresql.org
>> Subject: Re: [HACKERS] ARC patent
>>
>> >>>Neil Conway <[EMAIL PROTECTED]> writes:
>> >>>
>> >>>
>> FYI, IBM has applied for a patent on
With pg v7.4.7 I've written an SRF that uses SPI to return the results
of a query. It's one of those functions that works perfectly for me in
development but randomly crashes in production. Thus far I've been
unable to reproduce the crash. The problem is surely in my code. And
before I dig
Dave Held said:
>> -Original Message-
>> From: Marian POPESCU [mailto:[EMAIL PROTECTED]
>> Sent: Friday, April 01, 2005 8:06 AM
>> To: pgsql-hackers@postgresql.org
>> Subject: Re: [HACKERS] ARC patent
>>
>> >>>Neil Conway <[EMAIL PROTECTED]> writes:
>> >>>
>> >>>
>> FYI, IBM has applied
Dave Held wrote:
> Why would they have to do that? Why couldn't they just give a license
> for OSS distributions of PostgreSQL, and make commercial distributions
> obtain their own license for the ARC code? Doesn't IBM hire lawyers
> exactly for the purpose of writing complicated legal documents
> -Original Message-
> From: Bruce Momjian [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 01, 2005 10:23 AM
> To: Dave Held
> Cc: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] ARC patent
>
>
> Dave Held wrote:
> > > -Original Message-
> > > From: Marian POPESCU [mailto:[E
Dave Held wrote:
> > -Original Message-
> > From: Marian POPESCU [mailto:[EMAIL PROTECTED]
> > Sent: Friday, April 01, 2005 8:06 AM
> > To: pgsql-hackers@postgresql.org
> > Subject: Re: [HACKERS] ARC patent
> >
> > >>>Neil Conway <[EMAIL PROTECTED]> writes:
> > >>>
> > >>>
> > FYI, IBM
It's a bit tricky, since the machine I noticed it on is in production -
how would I test this on a test machine with little data?
Should I put the 8.0 tsearch2.so on my 7.4 production server?
Chris
Teodor Sigaev wrote:
I found several unpleasant blot in comparing functions and commit
changes to
> -Original Message-
> From: Marian POPESCU [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 01, 2005 8:06 AM
> To: pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] ARC patent
>
> >>>Neil Conway <[EMAIL PROTECTED]> writes:
> >>>
> >>>
> FYI, IBM has applied for a patent on ARC (AFA
> There is an updated survey of open source developers:
>
> http://flosspols.org/survey/survey_part.php?groupid=sd
>
It was very long, it says "45" questions, but many of those questions are
many parts with drop down menues.
Tedious!!
Also, it seems to be looking for sexual harrasment issues as
Russell Smith <[EMAIL PROTECTED]> writes:
> On Fri, 1 Apr 2005 05:40 pm, Michael Fuhr wrote:
>> I'd like to propose that we abandon the name "PostgreSQL" and rename the
>> project "Postgre", to be pronounced either "post-greh" or "post-gree".
> April 1 is nearly over.
Not on this side of the pond
Neil Conway <[EMAIL PROTECTED]> writes:
> Euler Taveira de Oliveira wrote:
>> Are you talking about DELETE FROM bar USING foo ? I submitted a patch
>> some months ago.
> At a quick glance, looks pretty good. It needs regression tests, and I'd
> also like to refactor the analyze.c additions to use
Gavin Sherry wrote:
> On Thu, 31 Mar 2005, Marian POPESCU wrote:
>
>
>>Tom Lane wrote:
>>
>>>Neil Conway <[EMAIL PROTECTED]> writes:
>>>
>>>
FYI, IBM has applied for a patent on ARC (AFAICS the patent application
is still pending, although the USPTO site is a little hard to grok):
>>>
>>>
Hi,
> > > Wow, seems I lost that somehow.
> >
> > BTW, I personally think it is fine for patch submitters to send
> "ping"
> > mails if your patch is not applied or reviewed within a reasonable
> > period of time -- this is standard practice among the GCC
> community,
> > for example. I certa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
> Uh, who exactly agreed to that? I know when I do \df it's generally
> to check out built-in functions not my own. I don't see this as an
> improvement.
Quoting Tom Lane:
> I thought the "S" suggestion was much better than this.
>
Thomas Hallgren wrote:
Richard Huxton wrote:
Michael Fuhr wrote:
I'd like to propose that we abandon the name "PostgreSQL" and rename the
project "Postgre", to be pronounced either "post-greh" or "post-gree".
This change would have a twofold purpose: it would meet popular demand,
and it would refle
Richard Huxton wrote:
Michael Fuhr wrote:
I'd like to propose that we abandon the name "PostgreSQL" and rename the
project "Postgre", to be pronounced either "post-greh" or "post-gree".
This change would have a twofold purpose: it would meet popular demand,
and it would reflect my next proposal, th
"Oleg Bartunov" writes
> One mystery remains, why stats show heap_blks_read > 0 for indexed search
?
> select 1 from foo where id=5
> I did pg_stat_reset() before run query.
>
There is no clustered index in PG so far, so all the data item has to be
stay in the heap. In brief, the executor ha
Michael Fuhr wrote:
I'd like to propose that we abandon the name "PostgreSQL" and rename the
project "Postgre", to be pronounced either "post-greh" or "post-gree".
This change would have a twofold purpose: it would meet popular demand,
and it would reflect my next proposal, that we abandon SQL as t
> I'd like to propose that we abandon the name "PostgreSQL" and rename the
> project "Postgre", to be pronounced either "post-greh" or "post-gree".
> This change would have a twofold purpose: it would meet popular demand,
> and it would reflect my next proposal, that we abandon SQL as the query
> l
On Fri, 1 Apr 2005 05:40 pm, Michael Fuhr wrote:
> I'd like to propose that we abandon the name "PostgreSQL" and rename the
> project "Postgre", to be pronounced either "post-greh" or "post-gree".
> This change would have a twofold purpose: it would meet popular demand,
> and it would reflect my ne
43 matches
Mail list logo
