Re: [HACKERS] problem importing languages in CVS tip
Hi Brandon, > Are we supposed to report bugs with the CVS tip of PostgreSQL, or are > we to assume that the developers are well aware of problems there and > are already working on them? You're supposed to report them! If we were aware of the problems, we'd fix them ;) Cheers, Chris ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] problem importing languages in CVS tip
Tom Lane <[EMAIL PROTECTED]> writes: > [I do not see that error] here. Try a full recompile. (Unless you > configure with --enable-depend, a "make distclean" is a smart move > during *any* update from CVS.) An initdb followed by rebuilding my tables fixed the problem. -- Brandon Craig Rhodes http://www.rhodesmill.org/brandon Georgia Tech[EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [HACKERS] problem importing languages in CVS tip
Brandon Craig Rhodes <[EMAIL PROTECTED]> writes: > Hmm. Now it is giving me that error even when I attempt a simple > `psql -l' which makes me wonder if I have done something horribly > wrong. Does anyone else see this? Not here. Try a full recompile. (Unless you configure with --enable-depend, a "make distclean" is a smart move during *any* update from CVS.) regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[HACKERS] problem importing languages in CVS tip
Are we supposed to report bugs with the CVS tip of PostgreSQL, or are we to assume that the developers are well aware of problems there and are already working on them? After my most recent CVS update I find that I cannot run createlang either to import the plpgsql nor the plpython languages - both attempts give the error message: ERROR: index_cost_estimator: invalid amcostestimate regproc createlang: external error at the client and ERROR: index_cost_estimator: invalid amcostestimate regproc on the server end. Hmm. Now it is giving me that error even when I attempt a simple `psql -l' which makes me wonder if I have done something horribly wrong. Does anyone else see this? -- Brandon Craig Rhodes http://www.rhodesmill.org/brandon Georgia Tech[EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
