Dear list,
in the documentation
(http://www.postgresql.org/docs/8.2/interactive/continuous-archiving.html)
is written that after doing the filesystem based backup, I have to
invoke pg_stop_backup() which triggers an xlog switch, and in order to
have a consistent backup, I need to have the switched
Hi
The server that hosts our production postgres databases had to be
rebooted last night as the file systems got remounted as read only.
After the reboot we re-started the databases but now nothing is getting
logged into the pglogs. Can you please assist us in figuring out the
problem and help re
Here are the messages from the pg_log before and after server reboot.
2007-10-10 06:22:50 CDT LOG: archived transaction log file
"000100700090"
2007-10-10 06:29:04 CDT LOG: autovacuum: processing database "nsc"
2007-10-10 06:34:58 CDT LOG: archived transaction log file
"000
Que tal:
Existe alguna versión de postgresql para Windows 64 bits?
Agradezco las atenciones al presente correo.
Saludos.
Hi,
I would like to read a blob from a PostgreSQL database, osing ODBS and
C++.
I have succeded to connect to the database, but i have no idea how to
read a certain blob.
If some one could help me with the readBlob() function, I would be
pleased
(for example just to read a string of 5 characters
Thomas Karcher <[EMAIL PROTECTED]> writes:
> My idea is now: When doing a consistent PITR backup, extend the
> documented steps between 4 (pg_stop_backup()) and 5 (wait for archived
> WAL file) with a busy wait on pg_xlog/archive_status/*.ready files - as
> soon as no .ready files are there anymore
"Bhella Paramjeet-PFCW67" <[EMAIL PROTECTED]> writes:
> Here are the messages from the pg_log before and after server reboot.
Uh, I don't see the problem? That looks like a perfectly normal
crash-recovery process, and it certainly doesn't seem to be the case
that "nothing is getting logged". Wha
Thomas Karcher <[EMAIL PROTECTED]> writes:
>> I believe the intended way to do this is to look at pg_stop_backup's
>> return value to determine the last segment you need to archive.
> Thank you - I saw that, but I didn't have a clue about how to determine
> the WAL filename in which this segment i
Hi Tom,
> > My idea is now: When doing a consistent PITR backup, extend the
> > documented steps between 4 (pg_stop_backup()) and 5 (wait for archived
> > WAL file) with a busy wait on pg_xlog/archive_status/*.ready files - as
> > soon as no .ready files are there anymore, the archiver has done it
Hi Tom,
> >> I believe the intended way to do this is to look at pg_stop_backup's
> >> return value to determine the last segment you need to archive.
> > Thank you - I saw that, but I didn't have a clue about how to determine
> > the WAL filename in which this segment is to be found ...
> Well, t
On Thu, 2007-10-11 at 16:37 +0200, Thomas Karcher wrote:
> Hi Tom,
>
> > > My idea is now: When doing a consistent PITR backup, extend the
> > > documented steps between 4 (pg_stop_backup()) and 5 (wait for archived
> > > WAL file) with a busy wait on pg_xlog/archive_status/*.ready files - as
> >
Hi Everybody,
I had a failure on stopping postgres.
The command I issued was:
>> pg_ctl stop -m s
and its response was:
>> waiting for server to shut
>> down... failed
>> pg_ctl: server does not shut down
I repeated the same command an
On 10/11/07, Tena Sakai <[EMAIL PROTECTED]> wrote:
>
>
>
> Hi Everybody,
>
> I had a failure on stopping postgres.
> The command I issued was:
> >> pg_ctl stop -m s
>
> and its response was:
> >> waiting for server to shut
> down...
>
Many thanks, Scott.
Tena Sakai
-Original Message-
From: Scott Marlowe [mailto:[EMAIL PROTECTED]
Sent: Thu 10/11/2007 10:03 AM
To: Tena Sakai
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] failure on 'pg_ctl stop' command
On 10/11/07, Tena Sakai <[EMAIL PROTECTED]> wrote:
>
>
>
> H
Hi, I'm new to 8.2 and trying to get our testing server to autovacuum.
I have a table that has roughly 116000 rows
I have applied 40,000 updates.
The applicable postgresql.conf parameters are as follows:
autovacuum| on
autovacuum_analyze_scale_fact
I created a test user with the following command:
$ createuser test
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create databases? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n
CREATE ROLE
This user at the moment does not have permission to
Hi List;
we have some monitoring/alert scripts which run sql against the database
(8.1.4) as a non-superuser. The problem is I get
when trying to access current_query from pg_stat_activity.
I ran these grant statements but still no joy:
grant select on pg_stat_activity to monitor_user;
grant
On Thursday 11 October 2007 12:33:24 Jessica Richard wrote:
> I created a test user with the following command:
>
> $ createuser test
> Shall the new role be a superuser? (y/n) n
> Shall the new role be allowed to create databases? (y/n) n
> Shall the new role be allowed to create more new roles? (
With this you give permission to a table
GRANT SELECT ON TABLE table TO user;
2007/10/11, Jessica Richard <[EMAIL PROTECTED]>:
> I created a test user with the following command:
>
> $ createuser test
> Shall the new role be a superuser? (y/n) n
> Shall the new role be allowed to create databases
Jessica Richard написа:
[...]
> Two questions:
>
> 1. How do I create a user with ONLY select permission but nothing else (not
> even creating any new tables)?
You could not create a read-only role by just using CREATE ROLE - you
could control the privileges that role has on particular DB objec
Hi Tom
After the server reboot nothing is getting logged by the postgres
database into pg_log like messages about archived log, autovacuum,
panic, alerts etc. The alerts from the pglogs get forwarded to our cell
phones and since no messages are getting logged we will not get notified
in case of a
"Bhella Paramjeet-PFCW67" <[EMAIL PROTECTED]> writes:
> After the server reboot nothing is getting logged by the postgres
> database into pg_log like messages about archived log, autovacuum,
> panic, alerts etc.
Sounds to me like you changed your logging settings...
regard
22 matches
Mail list logo
