> 05 22 * * 1-5 postgres /usr/bin/pg_dumpall -D >
> /disks/postgres/db.pg_dumpall
> connected to template1...
> /usr/bin/pg_dumpall: 0: Bad file descriptor
Filedescriptor 0 is STDIN. I would guess pg_dumpall want's to read something
from stdin, pherhaps ask you a question?
--
/Nils Höglund,
Nils Höglund wrote:
>
>> 05 22 * * 1-5 postgres /usr/bin/pg_dumpall -D >
>> /disks/postgres/db.pg_dumpall
>> connected to template1...
>> /usr/bin/pg_dumpall: 0: Bad file descriptor
>
> Filedescriptor 0 is STDIN. I would guess pg_dumpall want's to read
something
> from stdin, pherhaps ask y
usubscribe
su www.tim.it puoi iscriverti gratis alle TimNews, un modo rapido e tempestivo per
conoscere le ultime novita di TIM.
Hi,
I've got a problem which I can't find any answers for in the archives
(from simple searches at least) or on Google. I'm running Postgres 7.1.3
on RedHat Linux 7.2.
What I need to be able to do is this:
1. Dump a production database;
2. Create a development database;
3. Import the production
unsubscribe
su www.tim.it puoi iscriverti gratis alle TimNews, un modo rapido e tempestivo per
conoscere le ultime novita di TIM.
---
[EMAIL PROTECTED] (Bruce Momjian) wrote in message
news:<[EMAIL PROTECTED]>...
> Password prompting was changed in 7.2.X. You can now pass a script into
> psql, and you will be prompted for the password on your terminal rather
> than having the password coming from the script.
>
> The best way
Because, on error:
Too many clients already.
Regards,
Robson
from Brazil
keep in mind that cronjobs don't get your login environment, so things that
work in interactive mode often fail in cron unless you make sure to set up
the environment there too.
john guthrie
-Original Message-
From: Werner Modenbach [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002
Hello,
While I try to compile PostgreSQL 7.2.1 I get the following
error:
..
0x24
/opt/solaris_pd/PUBgcc-2.8.1/lib/libstdc++.a(streambuf.o)
0x18
/opt/solaris_pd/PUBgcc-2.8.1/lib/libstdc++.a(streambuf.o)
I downloaded postgresql 7.2.1 - rpm version, installed it to my Linux machine
and inputted some of my data in postgresql. Now I would like to re-configure
my postgresql server by increasing --enable-local and
--enable-multibyte=UNICODE options. How should I do?
I found all document talking ab
Nota: El mensaje reenviado fue adjuntado.
_
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com
--- Begin Message ---
hello, i`m a pgsql-admin, mi applications
Hi,
I've got a problem which I can't find any answers for in the archives
(from simple searches at least) or on Google. I'm running Postgres 7.1.3
on RedHat Linux 7.2.
What I need to be able to do is this:
1. Dump a production database;
2. Create a development database;
3. Import the production
> > Have you tried doing a network connection with your "apache" user? (su -
> > apache; psql -h localhost group3.)
>
> Yes, I've tried it and get the following:
>
> psql: could not connect to server: Connection refused
> Is the server running on host 192.168.1.2 and accepting
> TCP/I
Preston de Guise <[EMAIL PROTECTED]> writes:
> The procedure that I'm trying is:
> pg_dump production > production.dump
> dropdb development
> createdb development
> psql development -f production.dump
This looks okay to me. I assume you are running the psql session as the
database superuser?
Werner Modenbach <[EMAIL PROTECTED]> writes:
>> Filedescriptor 0 is STDIN. I would guess pg_dumpall want's to read
>> something from stdin, pherhaps ask you a question?
>>
> But it doesn't ask in interactive (shell) mode.
I was going to suggest that it's trying to read a password. Are you
sure
root wrote:
> I downloaded postgresql 7.2.1 - rpm version, installed it to my Linux machine
> and inputted some of my data in postgresql. Now I would like to re-configure
> my postgresql server by increasing --enable-local and
> --enable-multibyte=UNICODE options. How should I do?
> I found all
Guthrie, John wrote:
> keep in mind that cronjobs don't get your login environment, so things
that
> work in interactive mode often fail in cron unless you make sure to set up
> the environment there too.
>
Thanks John,
actually I didn't know that :-(
In the meantime I added the "http://archiv
Guthrie, John wrote:
> keep in mind that cronjobs don't get your login environment, so things that
> work in interactive mode often fail in cron unless you make sure to set up
> the environment there too.
That is very important to remember! First try adding "< /dev/null" to
the command. If tha
Werner Modenbach wrote:
> Guthrie, John wrote:
>
> > keep in mind that cronjobs don't get your login environment, so things
> that
> > work in interactive mode often fail in cron unless you make sure to set up
> > the environment there too.
> >
> Thanks John,
>
> actually I didn't know that :-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It will be slightly long story. You should obtain SRPM file first,
then extract the SRPM file in '/usr/src/redhat/SOURCES'
(in RedHat Linux for example) like as,
/usr/bin/rpm2cpio (SRPM file) | /bin/cpio -i
You could add the compile options to file
Alfred Anzlovar wrote:
> [EMAIL PROTECTED] (Bruce Momjian) wrote in message
>news:<[EMAIL PROTECTED]>...
> > Password prompting was changed in 7.2.X. You can now pass a script into
> > psql, and you will be prompted for the password on your terminal rather
> > than having the password coming fro
On Wed, 26 Jun 2002, [iso-8859-1] Rodrigo De la Peña wrote:
> hello, i`m a pgsql-admin, mi applications works, but
> after some time or transactions the db falls, when i´m
> trying to re-open the db y get this message:
>
> psql: could not connect to server: No buffer space
> avaible; the socket c
See if you can find out if the db is logging errors to a file or just
dumping things to standard out. It's pretty dependent on how your db is
started, but check if ps -ax shows anything like pg_ctl -l myfile or
postmaster > myfile. You might also want to check your postgresql.conf
file to see your
Mark-
If you're on version 7.1 or higher, the proffered way to turn on tcp/ip is
to add "tcpip_socket=true" to postgresql.conf in the data directory. (Then
restart.) Details are here:
http://www.postgresql.org/idocs/index.php?runtime-config.html
Regards,
-Nick
> -Original Message-
> Fr
Hello,
Exist field type date,
question:
With format date 'dd/mm/'
?
Regards,
I'm in the final stages of setting up database access for our domain
hosting customers. The current system is running PostgreSQL 7.0- with
which I haven't met any major problems (other than trying to figure out
how to restrict access to each domain's database- solved).
However... That box is sl
26 matches
Mail list logo
