Tom Lane wrote:
> Bruce Momjian writes:
> > Greg Sabino Mullane wrote:
> >> Specifically, LANGUAGE changes the headers of pg_controldata
> >> (but not the actual output, LC_ALL does that). Thanks for the
> >> nudge, I'll get to rewriting some code.
>
> > pg_upgrade does this in controldata.c fo
Bruce Momjian writes:
> Greg Sabino Mullane wrote:
>> Specifically, LANGUAGE changes the headers of pg_controldata
>> (but not the actual output, LC_ALL does that). Thanks for the
>> nudge, I'll get to rewriting some code.
> pg_upgrade does this in controldata.c for this exact reason:
>
Greg Sabino Mullane wrote:
[ There is text before PGP section. ]
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
>
> > Hmm, wouldn't have it been easier to set LC_MESSAGES to C before
> > calling pg_controldata?
>
> To be honest, I can't remember why that wasn't working for me when
Excerpts from Greg Sabino Mullane's message of vie jul 23 19:08:27 UTC 2010:
>
> Hash: RIPEMD160
>
> > Hmm, wouldn't have it been easier to set LC_MESSAGES to C before
> > calling pg_controldata?
>
> To be honest, I can't remember why that wasn't working for me when
> I tried it some time ago.
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Hmm, wouldn't have it been easier to set LC_MESSAGES to C before
> calling pg_controldata?
To be honest, I can't remember why that wasn't working for me when
I tried it some time ago. I just verified that it *will* work,
however, when I se
Excerpts from Greg Sabino Mullane's message of jue jul 22 13:34:25 UTC 2010:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> > Or you can use pg_controldata /path/to/pgdata and look
> > at "Time of latest checkpoint".
>
> Assuming your system is using English. Otherwise, you'll
>
Devrim GÜNDÜZ wrote:
What about adding a column to pg_stat_bgwriter, like "last_checkpoint"
or similar?
If you look at the messages I linked to, you'll find that's one of the
ideas that's been proposed and shot down. We even had a patch...
--
Greg Smith 2ndQuadrant US Baltimore, MD
Pos
On Tue, 2010-07-20 at 16:15 -0400, Greg Smith wrote:
> Devrim GÜNDÜZ wrote:
> > Is there a way to find last checkpoint time via SQL command? I know I
> > can grep xlogs by turning on log_checkpoints, but I'd prefer an SQL
> > solution.
> >
>
> Not directly. Best you can do without linking in n
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Or you can use pg_controldata /path/to/pgdata and look
> at "Time of latest checkpoint".
Assuming your system is using English. Otherwise, you'll
have to build a collection of .po strings as we did for
check_postgres.pl. Needless to say, I
On Tue, 2010-07-20 at 20:48 +0100, Thom Brown wrote:
>
> Or you can use pg_controldata /path/to/pgdata and look at "Time of
> latest checkpoint".
Right. Thanks :)
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Communi
Devrim GÜNDÜZ wrote:
Is there a way to find last checkpoint time via SQL command? I know I
can grep xlogs by turning on log_checkpoints, but I'd prefer an SQL
solution.
Not directly. Best you can do without linking in new server code is
either import the logs via CVS to get them into a tab
2010/7/20 Devrim GÜNDÜZ :
>
> Is there a way to find last checkpoint time via SQL command? I know I
> can grep xlogs by turning on log_checkpoints, but I'd prefer an SQL
> solution.
>
> --
Or you can use pg_controldata /path/to/pgdata and look at "Time of
latest checkpoint".
I don't know of any o
Is there a way to find last checkpoint time via SQL command? I know I
can grep xlogs by turning on log_checkpoints, but I'd prefer an SQL
solution.
--
Devrim GÜNDÜZ
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
PostgreSQL RPM Repository: http://yum.pgrpms.org
Community: devrim~Post
13 matches
Mail list logo
