On Sat, 2002-05-11 at 11:24, Tom Lane wrote:
> Hannu Krosing <[EMAIL PROTECTED]> writes:
> > Was it not the case that lazy vacuum had problems freeing tuples that
> > have toasted fields ?
>
> News to me if so.
>
> regards, tom lane
It looks like this may in fact be the ca
> The "setof" part is documented in src/backend/utils/fmgr/README.
> There's no good documentation for returning tuples at the moment,
> but basically you return a pointer to a TupleTableSlot. (Re-use
> the same slot on each call to avoid memory leakage.) There's an
> example in src/backend/exec
Tatsuo Ishii wrote:
> Does your SRF function allow to return a setof composite data type
> using C function? If so, how can I write such that C function? I
Just to follow-up, here's a quick look at what works and what doesn't,
at least using my test script.
SELECT * FROM myfunc();
Language
Ret
Tatsuo Ishii wrote:
> Does your SRF function allow to return a setof composite data type
> using C function? If so, how can I write such that C function? I
> couldn't find any example or explanation so far. You referred dblink,
> but in my understanding it does not have any function that returns a
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Does your SRF function allow to return a setof composite data type
> using C function? If so, how can I write such that C function?
The "setof" part is documented in src/backend/utils/fmgr/README.
There's no good documentation for returning tuples at the
Does your SRF function allow to return a setof composite data type
using C function? If so, how can I write such that C function? I
couldn't find any example or explanation so far. You referred dblink,
but in my understanding it does not have any function that returns a
setof composite data type.
On Sat, 18 May 2002 19:45:30 -0400
"Tom Lane" <[EMAIL PROTECTED]> wrote:
> Joe Conway <[EMAIL PROTECTED]> writes:
> > Since the sequence-specific operations are really just function calls,
> > maybe it should be:
> > SELECT: read sequence as a table
> > EXECUTE: all sequence-specific ope
Joe Conway <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> what we really have is:
>>
>> SELECT: read sequence as a table
>> UPDATE: all sequence-specific operations.
> Since the sequence-specific operations are really just function calls,
> maybe it should be:
> SELECT: read sequence a
Tom Lane wrote:
>
> "SELECT" still means what it says: the ability to do a select from
> the sequence, which lets you see the sequence parameters. So what
> we really have is:
>
> SELECT: read sequence as a table
> UPDATE: all sequence-specific operations.
>
Since the sequence-spe
Joel Burton wrote:
> For those who want to play on the bleeding edge of CVS, can someone
> provide the syntax for the recently-checked-in set-returning
> functions? I've got it figured out when I'm returning a many rows of
> single column, but not for many rows of several columns.
For multipl
On Sat, 18 May 2002, Tom Lane wrote:
> "Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> > This feature could be added to PgAccess but I felt it was general
> > enough to be placed in the interface library. I think someone else
> > suggested such a place a couple of weeks ago also. If there is a
>
> Bear Giles <[EMAIL PROTECTED]> writes:
> > 1) add SASL. This is a new standards-track protocol that is often
> >described as "PAM" for network authentication.
>
> To me, "new standards-track protocol" translates as "pie in the sky".
> When will there be tested, portable, BSD-license librar
> I'm not that clueful about SASL -- would this mean that we could get
> rid of the PostgreSQL code that does SSL connections, plus MD5, crypt,
> ident, etc. based authentication, and instead just use the SASL stuff?
We would still need the ability to map user identities -> pgusers for
those meth
"Nigel J. Andrews" <[EMAIL PROTECTED]> writes:
> This feature could be added to PgAccess but I felt it was general
> enough to be placed in the interface library. I think someone else
> suggested such a place a couple of weeks ago also. If there is a
> concensus that this should be done in the app
Bear Giles <[EMAIL PROTECTED]> writes:
> 1) add SASL. This is a new standards-track protocol that is often
>described as "PAM" for network authentication. PostgreSQL could
>remove *all* protocol-specific authentication code and use
>standard plug-in libraries instead.
To me, "new st
"Joel Burton" <[EMAIL PROTECTED]> writes:
> Tom Lane <[EMAIL PROTECTED]> said:
>> ISTM the reason we've not addressed this for so long is that no one
>> could think of a reasonable way to solve it on the backend side.
>> Maybe we just have to shift our focus.
> Out of curiosity, Tom, why the pref
On Sat, 18 May 2002 11:39:51 -0600 (MDT)
"Bear Giles" <[EMAIL PROTECTED]> wrote:
> 1) add SASL. This is a new standards-track protocol that is often
>described as "PAM" for network authentication. PostgreSQL could
>remove *all* protocol-specific authentication code and use
>standard
For those who want to play on the bleeding edge of CVS, can someone provide the syntax
for the recently-checked-in set-returning functions? I've got it figured out when I'm
returning a many rows of single column, but not for many rows of several columns.
If someone can do this, and no one has p
Tom Lane <[EMAIL PROTECTED]> said:
> "Joel Burton" <[EMAIL PROTECTED]> writes:
> > Given that 98% of my function defining is done is psql, this would be
> > fine for me and solve my frustrations. It wouldn't help people that
> > build functions in scripting languages or non-psql environments,
> >
This is similar to the same patch as I submitted Thursday, and hopefully
withdrew in time after a response was made. I have repeated the description
with appropiate changes for ease of reference.
I've attached a patch for libpgtcl which adds access to backend version
numbers.
This is via a new
I came across another bug in the SSL code. backend/libpq/pqcomm.c:pq_eof()
calls recv() to read a single byte of data to check for EOF. The
character is then stuffed into the read buffer.
This will not work with SSL. Besides the data being encrypted, you
could end up reading a byte from an SSL
[My apolgies if this turns up in the lists twice (now three times) but my
mailer claims it's been in the queue for them too long. Not sure why it
thinks that since it's only a few minutes since I sent it.]
On Fri, 17 May 2002, Peter Eisentraut wrote:
> Nigel J. Andrews writes:
>
>
I've been looking at the authentication and networking code and
would like to float a trial balloon.
1) add SASL. This is a new standards-track protocol that is often
described as "PAM" for network authentication. PostgreSQL could
remove *all* protocol-specific authentication code and use
Dear all,
I would like to transform UTF-8 strings into Java-Unicode. Example :
- Latin1 : 'é'
- UTF-8 : 'é'
- Java Unicode = '\u00233'
Basically, a Unicode compatible ascii() function would be fine.
ascii('é') should return 233.
1) Has anyone written an ascii UTF-8 safe wrapper to ascii() fu
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> But shouldn't it more ideally be
> currval: SELECT
> nextval: SELECT + UPDATE
> setval: UPDATE
> because nextval allows you to infer the content of the sequence? (Cf.
> UPDATE tab1 SET a = b requires SELECT + UPDATE on tab1.)
One o
It means you are running a jdbc driver from 7.2 (perhaps 7.1, but I
think 7.2) against a 6.5 database. While we try to make the jdbc driver
backwardly compatable, we don't go back that far. You really should
consider upgrading your database to something remotely current.
thanks,
--Barry
[EM
Lincoln Yeoh <[EMAIL PROTECTED]> writes:
> How about the postgresql logo - is there a source vector/postscript of it
> so that he can blow it up without res loss and print it?
I have EPS versions of both the elephant-in-crystal and cartoon-elephant
logos. I'm pretty sure both are up on the webs
The documentation of the sequence privileges on the GRANT reference page
doesn't match the code.
Documented:
currval:UPDATE
nextval:UPDATE
setval: UPDATE
Actual:
currval:SELECT
nextval:UPDATE
setval: UPDATE
But shouldn't it more ideally be
curr
"Joel Burton" <[EMAIL PROTECTED]> writes:
> Given that 98% of my function defining is done is psql, this would be
> fine for me and solve my frustrations. It wouldn't help people that
> build functions in scripting languages or non-psql environments,
> however, but I don't know how common this is.
Tom Lane <[EMAIL PROTECTED]> said:
> Seems like the only way to do that in the backend would be to find a way
> of slipping the function text past the lexer/parser entirely. While I
> can imagine ways of doing that, I think it'd be a *whole* lot cleaner
> to fix things on the client side.
>
> H
On Friday 17 May 2002 22:16, you wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Might be an idea to create a pgsql-hackers-win32 list also? Or just
> > pgsql-win32?
>
> Actually, I think that'd be a bad idea. The very last thing we need is
> for these discussions to get fragmented.
How about the postgresql logo - is there a source vector/postscript of it
so that he can blow it up without res loss and print it? The logo designer
may still have the source files.
Cheerio,
Link.
At 02:56 AM 5/18/02 -0300, Marc G. Fournier wrote:
>Not that I'm aware of anyone making ...
>
>O
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: 18 May 2002 00:01
> To: Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: More schema queries
>
> There was already some discussion about making a variant version of
> current_schemas() that would tell you the Who
33 matches
Mail list logo
