Hi all,
Oups, I forgot to put the ML in copy of my reply :-(
[...]
> > ERROR: fmgr_info: function 16594: cache lookup
> failed
> Most likely this means something happened to the
> call handler function
> for plpgsql. Look in pg_language to see the
> "lanplcallfoid" value for
> plpgsql; is i
--- Tom Lane <[EMAIL PROTECTED]> a écrit :
> Well, that looks reasonable, but what's its OID?
> (should've asked for
> select oid,* from ...)
scheduling=# select oid, * from pg_proc where
proname='plpgsql_call_handler';
oid | proname| proowner | prolang |
proisinh | proistrus
> > update pg_language set lanplcallfoid=374578 where
> > lanname='plpgsql';
>
> > Is it correct ?
>
> Right.
Ok, it's working fine now.
Thanks you very very much.
Bye
Laurent
=
The misspelling master is on the Web.
_100 % Dictionnary Free !
//(
/ Dico / /
The following bug has been logged online:
Bug reference: 3000
Logged by: laurent faillie
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.3
Operating system: HP-UX 11.11
Description:Linking problem
Details:
Hello,
Even if the compilation succeed, psql
The following bug has been logged online:
Bug reference: 3271
Logged by: laurent faillie
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2.4
Operating system: HP-UX 11.11 (v32 bits).
Description:PREPARE/EXCUTE don't work
Details:
Hi all,
While trying t
Hi Heikki,
--- Heikki Linnakangas <[EMAIL PROTECTED]> a
écrit :
> > www=> PREPARE authn_dbd_1 (varchar) AS select mdp
> from mariage.comptes where
> > nom = '$1';
>
> That $1 should be without the quotes, like this:
>
> PREPARE authn_dbd_1 (varchar) AS select mdp from
> mariage.comptes where
>
Hi,
I have patched pg_dump.c to have a correct output file
when the database use procedure langages.
Bye
Laurent
PS: I have tryed to send the full source code as
attachement but my message never appear in this ML, so
I hope this diff file is enought ...
diff
603a604,606
> Move
--- Bruce Momjian <[EMAIL PROTECTED]> a écrit :
>
> Can I get a context diff (diff -c) of this?
Ok, but you have to wait 'till end of next week
because I'm on hollidays (SSSskki :- ).
> What
> exactly did you
> change and why?
Ok, some explanations :
> > 603a604,606
> > > Mov
Ok there is the context diff of my modification :
Bye
Laurent
---
*** postgresql-7.3.2/src/bin/pg_dump/pg_dump.c Fri Dec
27 18:10:55 2002
--- postgresql-7.3.2/src/bin/pg_dump/pg_dump.c.new Wed
Mar 5 12:12:32 2003
***
*** 601,606
--- 601,609
Hi Tom,
First of all, I appologies for my english : it's not
my native language so, it's not so easy for me :-(
> > ... yes but it is not the probleme : as no user is
> > attached w/ procedural languages (it's clearly
> > commented in the source code of pg_dump), it
> should
> > generate ACL of
--- Bruce Momjian <[EMAIL PROTECTED]> a écrit :
>
Hello Bruce,
> Well, we do dump/load procedural languages before
> function, as you can
> see in your output. The plpgsql has TOC #247 while
> the create language
> has TOC #252.
Please have a look in another message I made in this
mailling li
--- Bruce Momjian <[EMAIL PROTECTED]> a écrit :
>
> Your patch has been added to the PostgreSQL
> unapplied patches list at:
>
> http://momjian.postgresql.org/cgi-bin/pgpatches
>
> I will try to apply it within the next 48 hours.
Ok, thanks a lot.
Have a nice day.
Laurent
=
The m
Hi Bruce,
I duno where is the problem, because :
1/ if I do a simple CREATE SEQUENCE x; as you do, the
output is ok,
2/ It works also if I do a
CREATE SEQUENCE x
START 1
INCREMENT 1
MAXVALUE 2147483647
MINVALUE 1
CACHE 1;
which is the command used to recreate seq_id_fch wh
Ok, I found what's append :
1/ current value of the sequence data are following :
scheduling=# select * from seq_id_fch;
sequence_name | last_value | increment_by | max_value
| min_value | cache_value | log_cnt | is_cycled |
is_called
---++--++---
Hello Bruce,
there is a contextual diff of my patch w/ the current
(I hope) snapshot of postgresql.
I test it on my own database, but I found another bug
w/ SEQUENCE this time. I have created a new ticket,
#918 for this as it's totaly a separate problem.
Bye
Laurent
--
*** pg_dump.c.org
CAUTION : don't open the attachment of this incident,
because it seems it contains a VIRUS.
--- [EMAIL PROTECTED] a écrit : > Please see the
attached zip file for details.
> ATTACHMENT part 2 application/x-zip-compressed
name=your_details.zip
__
Hi all,
Is it possible to improve "configure" script of
postgresql to allow to specify in which directory a
3rd tool is installed ?
An option like --with-zlib=[DIR] is very usefull
because w/ the current (7.4.1) configure script, you
have to set by yourself some variables to specify
where is inst
Hi Tom,
--- Tom Lane <[EMAIL PROTECTED]> a écrit : >
=?iso-8859-1?q?Laurent=20FAILLIE?=
> <[EMAIL PROTECTED]> writes:
> > Is it possible to improve "configure" script of
> > postgresql to allow to specify in which directory
> a
> > 3rd tool is installed ?
>
> See --with-includes and --with-libra
Hi Tom,
> --- Tom Lane <[EMAIL PROTECTED]> a écrit :
>
> > > creating system views... ERROR: did not find
> '}'
> > at end of input node
> >
> > Hmm. This would seem to indicate a mismatch
> between
> > the nodeToString
> > and stringToNode routines (outfuncs.c and
> > readfuncs.c), which is
--- Tom Lane <[EMAIL PROTECTED]> a écrit : >
> Hm. It's starting to sound like an actual bug ---
> though whether it's
> in HPUX 11.00, gcc, or Postgres is difficult to
> guess.
Arg :-(
> The Postgres
> code is certainly known to work on many platforms,
> but it could have
> an unsuspected p
--- Tom Lane <[EMAIL PROTECTED]> a écrit :
> > creating system views... ERROR: did not find '}'
> at end of input node
>
> Hmm. This would seem to indicate a mismatch between
> the nodeToString
> and stringToNode routines (outfuncs.c and
> readfuncs.c), which is
> something we don't normally
--- Raghavendra HR <[EMAIL PROTECTED]> a écrit :
> Hello,
[...]
> checking for int timezone... yes
> checking types of arguments for accept()...
>
> .**Stops here with the
> error.**
>
> Pls. help me installing the same on HPUX11.11
> Wai
22 matches
Mail list logo
