At 2:05a -0400 on 12 Jun 2007, Johannes Konert wrote:
> that was a good hint. Suids are not working on bash-scripts, but with a
> restricted entry in /etc/sudoers now the backup-user can execute a
> copy-and-access-script to get the files from within PGDATA-dir.
If you're curious as to /why/ setui
Oliver Elphick wrote:
You could run the backup as postgres and pipe the output to another
program owned by the other user and with suid set in its permissions.
The suid means that the receiving program would have access where you
don't want postgres to go.
Thanks Oliver,
that was a good hint. Su
On Mon, 2007-06-11 at 09:03 +0200, Johannes Konert wrote:
> Joshua D. Drake wrote:
> > Anything else in there you should be grabbing via pg_dump anyway.
> So you suggest not to backup the filesystem-files, but to do a dump
> instead? Does this work together with PITR as described in 23.3.
> (ht
Joshua D. Drake wrote:
Johannes Konert wrote:
But that is not my point. The question is where I can change the
enforced chmod 700 postgresql always wants me to set.
You can't.
You can however change the postgresql.conf to put look for files
somewhere besides $PGDATA and thus you would be able
Johannes Konert wrote:
Ragnar wrote:
are you planning a filesystem-level backup?
As war as I understood the docu of psql 8.2.4
(http://www.postgresql.org/docs/8.2/interactive/continuous-archiving.html
section 23.3.2) you can copy the files while postgres is running
(respecting pg_start_backup
On Thu, 2007-06-07 at 12:57 +0200, Johannes Konert wrote:
> > use sudo in your backup scenario, or run you backup as postgres
> >
> Thanks for your quick reply.
> Unfortunaltelly runing backup via sudo is not an option due to sercurity
> issues and using postgres-user is not feasable because ot
Ragnar wrote:
are you planning a filesystem-level backup?
are you aware that you cannot just backup the postgres data directories
fro under a running server, and expect the
backup to be usable?
gnari
As war as I understood the docu of psql 8.2.4
(http://www.postgresql.org/docs/8.2/intera
use sudo in your backup scenario, or run you backup as postgres
Thanks for your quick reply.
Unfortunaltelly runing backup via sudo is not an option due to sercurity
issues and using postgres-user is not feasable because other data as
well is backuped where postgres-user should not have ac
On fim, 2007-06-07 at 10:38 +0200, Johannes Konert wrote:
> Hi postgresql-listmembers,
> for a backup-scenario I need to have access to the pgdata-directory as a
> different shell-user, but postgresqul refuses to start if chmod is not
> 700 on the directory.
>
> Is there a way to prevent postgr
Hi postgresql-listmembers,
for a backup-scenario I need to have access to the pgdata-directory as a
different shell-user, but postgresqul refuses to start if chmod is not
700 on the directory.
Is there a way to prevent postgres to check the data-dirs chmod 700 on
startup (and while running) ?
10 matches
Mail list logo
