On Tuesday 28 July 2009 03:22, Albe Laurenz wrote:
> Terry Lee Tucker wrote:
> > Does anyone know if a function written in C and linked into the backend
> > in a shared library with a statically declared structure, maintain that
> > data for the life of the backend process such that, when the funct
Terry Lee Tucker wrote:
> Does anyone know if a function written in C and linked into the backend in a
> shared library with a statically declared structure, maintain that data for
> the life of the backend process such that, when the function is called again,
> the structure data is intact?
>
On Tue, Feb 3, 2009 at 6:16 PM, Tom Lane wrote:
> Merlin Moncure writes:
>> On Tue, Feb 3, 2009 at 4:28 PM, Tom Lane wrote:
>>> You know, maybe we should stop holding our noses and do something about
>>> this old gotcha. That type's not going away anytime soon, but could we
>>> rename it to cha
Tom Lane writes:
> Alvaro Herrera writes:
>> Grzegorz Jaśkiewicz wrote:
>>> looks like it really has to be defined with "char" in double quotes. I
>>> thought just char is enough...
>
>> They're different types.
>
> You know, maybe we should stop holding our noses and do something about
> this
Merlin Moncure writes:
> On Tue, Feb 3, 2009 at 4:28 PM, Tom Lane wrote:
>> You know, maybe we should stop holding our noses and do something about
>> this old gotcha. That type's not going away anytime soon, but could we
>> rename it to char1 or something like that? (With some sort of backward
On Tue, Feb 3, 2009 at 9:28 PM, Tom Lane wrote:
> On the other hand, that might be more trouble than it's worth. Even
> with a domain alias, there'd be a nontrivial chance of breaking apps
> that look at the char columns of the system catalogs.
I have to apologize, it is clearly written in quo
looks like it really has to be defined with "char" in double quotes. I
thought just char is enough...
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, Feb 3, 2009 at 4:28 PM, Tom Lane wrote:
> Alvaro Herrera writes:
>> Grzegorz Jaśkiewicz wrote:
>>> looks like it really has to be defined with "char" in double quotes. I
>>> thought just char is enough...
>
>> They're different types.
>
> You know, maybe we should stop holding our noses a
it's defined:
create or replace function filter_text(text, char) returns text as
'test_proc.so' language 'c';
which leads me to another question.
It seems that I have to leave psql and comeback, for new version to be
loaded. (that's on 8.4 tho, I don't have 8.3 at home).
And also that 'replace'
Alvaro Herrera writes:
> Grzegorz JaÅkiewicz wrote:
>> looks like it really has to be defined with "char" in double quotes. I
>> thought just char is enough...
> They're different types.
You know, maybe we should stop holding our noses and do something about
this old gotcha. That type's not go
Grzegorz Jaśkiewicz wrote:
> looks like it really has to be defined with "char" in double quotes. I
> thought just char is enough...
They're different types.
--
Alvaro Herrera http://www.flickr.com/photos/alvherre/
"Crear es tan difícil como ser libre" (Elsa Triolet)
--
Alvaro Herrera writes:
> Grzegorz JaÅkiewicz wrote:
>> for whatever reason, taht doesn't return the real char that was passed in.
> Yeah ... try DatumGetBpCharP instead. PG_GETARG_CHAR is for type "char"
> with quotes, which is a completely different thing.
Or maybe the C code does just what h
Grzegorz Jaśkiewicz wrote:
> > char c = PG_GETARG_CHAR(1);
>
> for whatever reason, taht doesn't return the real char that was passed in.
Yeah ... try DatumGetBpCharP instead. PG_GETARG_CHAR is for type "char"
with quotes, which is a completely different thing.
--
Alvaro Herrera Valdiv
> char c = PG_GETARG_CHAR(1);
>
for whatever reason, taht doesn't return the real char that was passed in.
--
GJ
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
14 matches
Mail list logo
