> As for those OS wars - are there any serious Linux sysadmins who don't
> have a copy of "Linux System Security" next to the server?
I run Linux on everything, and I don't have a copy of that book next to
any of my machines. Then again, I don't run Redhat.
John
I'm glad someone else found out
about it first. :)
I think functionality to retrieve the necessary libs ought to be built
into the installation of DBD::Pg to facilitate just such a situation...
John
--
# John Madden [EMAIL PROTECTED] ICQ: 2EB9EA
# FreeLists, Free mailing lists for
> ok, makes sense, so how would I get around it? Thanks,
You type in the username/password as if the prompts were there. :)
John
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
> All I want to do is dump the db, which should be easy, right? If I do:
> pg_dump -u worldwide > worldwide.pgdump
pg_dump, with the -u, expects you to enter your username/password to
stdin or something. (guys, print the prompts to STDERR instead?) The
problem is that stdout is redirected into
gres cope with this? (How is the support for
> big data fields now BTW?)
It works quite well (designing a web-based system on it right now), but
because of a DDB::Pg limit, I can only get 8k into a 'text' field. So if
your app is web-based, you might want to not use perl...
John
y a little difficult
when you can't insert more than 8k.
Does anyone know why this limit exists, or if there's a way around it?
John
--
# John Madden [EMAIL PROTECTED] ICQ: 2EB9EA
# FreeLists, Free mailing lists for all: http://www.freelists.org
# UNIX Systems Engineer
killed by SIGSEGV +++
gdb says:
Program received signal SIGSEGV, Segmentation fault.
0x40019fbe in pg_password_sendauth () from
/usr/local/pgsql/lib/libpq.so.2.1
I haven't ever had a problem with Postgres until today, and I'm quite
stumped with it. All of my installs are default compile
