-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Happened to me too sometime.
If you look at the messages generated by your import you should see errors
complaining about the missing plpgsql handler. If there is no handler the
procedures will not be imported. The import code usually has something to
install the handler, but on my system this didn't work because of access
rights.
Therefor what I do now is to initialize the new database and add the handlers
for the stored procedures. After that any user can import the file without
errors.
Hope that helps
UC
On Wednesday 21 January 2004 02:29 pm, lnd@hnit.is wrote:
> After copied pg database from one PC to another
>
> -I could not find plpgsql function(s) in the copied database.
> -had to instal plpgsql language handler again
>
> -whilst tables and data moved fine
>
> The copy included all under /cygwin/usr/local/pgsql/data and database was
> down while making a copy.
>
>
> What could I forget to copy as far plpgsql is concerned ?
> Are pgsql stored objects stored in the database itself (a table pg_proc,
> column prosrc)?
> Catalog tables like pg_proc are just a part of database cluster data files,
> aren't they?
>
> Thank you in advance, Laimis
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
- --
UC
- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFADwHMjqGXBvRToM4RAqiJAKDKCsui92pz4SwbKAZyap5ahS8NbQCgiHrD
gvP/Skyt92IXdSzXvoZIdJI=
=yXmU
-----END PGP SIGNATURE-----
