- Original Message -
From: <[EMAIL PROTECTED]>
Subject: [ADMIN] Problems with remote access
> a table. It didn't work at all. I can see records on a grid, but the
system
> doesn't allow me to make any changes (INSERT, DELETE or UPDATE). Can
anyone
> of you tell me why and what can I do t
Hi,
I've been using Postgres locally in an Win95 + Delphi environment.
Everything is fine. Now, I wanted to access the database remotelly. I
installed the ODBC driver in another micro and tried to insert a record in
a table. It didn't work at all. I can see records on a grid, but the system
doesn
Thanks a lot. Your solution fixed the problem. Glad to be a part of such a
knowledgeable mailing list.
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 27, 2001 5:43 PM
> To: root
> Cc: [EMAIL PROTECTED]
> Subject: Re: [ADMIN] Postgres Startup troubl
root <[EMAIL PROTECTED]> writes:
>> action "Starting PostgreSQL: " su -l $PGUSER -c "$DAEMON start -D '$PGDATA' -l
>$PGLOG"
I dunno what "action" is, but I'll bet that the problem with this script
is that the arguments of su end up getting scanned twice in the shell
script, once when action is c
I can't start postgres using a modified form of the startup script
supplied in the contrib directory. I keep getting an error from su
saying that "D is an invalid option."
Below is the entire script:
> #! /bin/sh
>
> # This is an example of a start/stop script for SysV-style init, such
> # as i
[EMAIL PROTECTED] writes:
> Problem is that vacuum still failed with an out of disk space
> message. Anyone knows on how much a table needs to be vacuumed correctly ?
> (A 20GB table with 4GB indexes did not vacuum in 50GB of free space).
Update to 7.1.3, or apply the patch that was posted back
