Can I stop the server and modify recovery.conf with this param and restart
it again without problems?
Thanks a lot.
2013/5/22 Raghavendra
> On Wed, May 22, 2013 at 3:38 PM, Fabio Rueda Carrascosa <
> avances...@gmail.com> wrote:
>
>> hello , I'm restoring a 7 days ag
hello , I'm restoring a 7 days ago full backup + wal files. I have to
recover more than 6k wal files and I have no time, I would accept to work
with a ~ 3 days ago snapshot, can I stop the recovery process and start the
server?, if yes, how?
My recovery.conf file only has this line :
restore_com
As usual, you are totally right Tom.
But thanks everybody for the debate. Only I have to add, is near a "must"
to run with --check before actually run the command.
2013/5/16 Tom Lane
> Fabio Rueda Carrascosa writes:
> > Hello, I have a 9.1 cluster with 50 databases, on
Hello, I have a 9.1 cluster with 50 databases, only one table per db with
2000 rows only, but a lot of schema around each one (postgis databases)
The old cluster size is 1GB
du -chs /var/lib/postgresql/9.1/main/
1.1G
now I run a pg_upgrade to 9.2 with hard link mode,
pg_upgrade --link \
--
My grant/revoke architecture is fine, you mean about costly cpu/ram queries?
2013/4/9 Tom Lane
> Fabio Rueda Carrascosa writes:
> > Im planning to publish my postgresql server to a few untrusted clients.
> > I dont want them to modify any runtime setting, like work_mem
Im planning to publish my postgresql server to a few untrusted clients.
I dont want them to modify any runtime setting, like work_mem or something
risky to my server. In general I assume the pg_catalog schema is public but
I don't want to allow updating pg_settings at all.
Is it possible?
