Tom Lane wrote:
=# select distinct prolang from pg_proc;
prolang
-
12
13
14
17813
63209
63212
63213
63214
(8 rows)
That looks fine ...
=# select * from pg_language ;
Try "select oid,lanname from pg_language".
regards, tom lane
Sorry, I see that I forg
Bricklen Anderson <[EMAIL PROTECTED]> writes:
> =# select distinct prolang from pg_proc;
> prolang
> -
>12
>13
>14
> 17813
> 63209
> 63212
> 63213
> 63214
> (8 rows)
That looks fine ...
> =# select * from pg_language ;
Try "select oid,lanname
Tom Lane wrote:
Bricklen Anderson <[EMAIL PROTECTED]> writes:
Once I recompile the function, I no longer get that message. Is there
anything else that I can check or do to make this stop happening? Or is
this a sign of things to come (possible corruption, etc?)
Well, the original error sounds li
Bricklen Anderson <[EMAIL PROTECTED]> writes:
>> Once I recompile the function, I no longer get that message. Is there
>> anything else that I can check or do to make this stop happening? Or is
>> this a sign of things to come (possible corruption, etc?)
Well, the original error sounds like a di
Bricklen Anderson wrote:
Hi listers!
I'll start with some details:
select version();
PostgreSQL 8.0.0 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5
(Debian 1:3.3.3-5)
Upon compiling a new function that I was working on, I came across an
error:
"could not read block 0 of relation 1663/172
Hi listers!
I'll start with some details:
select version();
PostgreSQL 8.0.0 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5 (Debian
1:3.3.3-5)
Upon compiling a new function that I was working on, I came across an error:
"could not read block 0 of relation 1663/17239/16709: Bad address" whi
