e following select statement,
>
> select pg_class.oid, pg_trigger.tgrelid from pg_trigger left join pg_class
> on pg_trigger.tgrelid=pg_class.oid;
>From the error message it appears you have a data type called "trigger",
which appears to be invalidated.
--
Simon Riggs
ried to supply a wrong login password, and the login failure was
> successfully logged). Has anyone experienced similar issue?
Yes, its not very easy to determine if it is working, and if it is, what
it has done.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---
On Fri, 2007-01-05 at 12:59 -0600, Ben K. wrote:
> 2. sql dump and PITR
>
> Is it possible to use the PITR method with SQL dump? (pg_start_backup ->
> sql dump -> pg_stop_backup) I guess not, but just want to make sure.
>
No, because there is no reason or benefi
t. So there's nothing to
stop you doing a recovery on a development machine up to a certain
point, then dumping the deleted data using pg_dump and re-loading it
into the live server. Then erasing the dev recovered database.
--
Simon Riggs
EnterpriseDB http://www.enterpri
On Tue, 2007-01-09 at 08:37 -0600, Ben K. wrote:
> On Mon, 8 Jan 2007, Simon Riggs wrote:
>
> > There is a log analysis tool on pgfoundry that does something similar.
>
> > You can already stop recovery at a certain point. So there's nothing to
> > stop you d
the cluster on a second server to your specific point in
> time, and restore that copy of the database in question to your primary
> server.
I'll take that as a request for a TODO item, for 8.4
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---
very well at all, since many records depend upon
previous data changes, so could quickly end in further errors.
What would you suggest?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
s/8.2/static/warm-standby.html
If you want to do (a) or (b) you've mistakenly read both parts of the
manual and if you want to do (c) then you need two servers, not just
one.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
--
the point-in-time it has
stopped at sounds blindingly obvious in retrospect.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
t; of WAL. But in this case it looks more like corrupt data ...
Tom,
I think there is a problem here. If we stop before the end of logs we
should be incrementing the timeline id.
I'm not going to think about it right now, but I'll think on that next
week. Not the most likely
On Fri, 2007-03-30 at 12:40 -0400, Tom Lane wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > I think there is a problem here. If we stop before the end of logs we
> > should be incrementing the timeline id.
>
> There is no good reason here to think tha
h 8.2 also, though isn't available
as part of the 8.2 distribution. The README will contain information for
both 8.2 and 8.3 releases, since there will be one minor difference.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of bro
. I might try patching pg_standby.c if no
> one beats me to it.
I'll look at doing this.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please
D yet, or
> is there somewhere else I should be looking?
Not in HEAD (yet?)
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by
The use-case for Warm Standby is for people that want a simple,
efficient mechanism for providing High Availability replication.
If there are any feature requests, please let me know.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadca
executed statement, so that's not a solution.
http://pgfoundry.org/projects/xlogviewer/
I'd appreciate some feedback. I'll be looking to release a new version
within next few months.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
On Wed, 2007-04-25 at 13:13 -0400, Pascal Robert wrote:
> Le 07-04-25 à 11:43, Simon Riggs a écrit :
>
> > On Wed, 2007-04-25 at 11:28 -0400, Pascal Robert wrote:
> >
> >> I'm writing our backup procedure for using WAL and PITR, but to be
> >> able to d
> you'll
> > need to search ahead/behind.
>
> Ok, so I guess that auto commited statements will never have date/time ?
There'll be a COMMIT record for every transaction, however it was
initiated, unless the server crashed/shutdown before it could be issued.
--
en?
Can you start from the beginning again and describe exactly what set of
circumstances you're in. I want to remove any bug or doubt that there is
one lurking.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)
On Fri, 2007-06-01 at 12:02 +0100, Simon Riggs wrote:
> On Thu, 2007-05-31 at 16:09 +0100, Jon Colverson wrote:
> > >
> > >> This looks like a bug to me. Any thoughts?
> > >
>
> > No; nothing is touching the archive except for the archive_comm
ieve it has more to do with the cost of removing each row from the
index, which might then require parent uplink updates also, which is a
major source of contention. DB2 type 2 indexes deliberately avoid that
issue, and opt for an approach that requires an offline utility to clear
up af
On Sat, 2007-06-02 at 01:07 +0100, Jon Colverson wrote:
> Simon Riggs wrote:
> > I've spent some time re-examining the code and I can't see a route for
> > the discussed problem to occur. All the main code paths do not exhibit
> > this problem in 8.2, so I&#
05D)
Please send the history file, plus give your best understanding of the
previous history of this database's crashes/recoveries.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Do
On Thu, 2007-06-07 at 08:50 +0100, Simon Riggs wrote:
> On Wed, 2007-06-06 at 23:31 -0700, Jerry Huff wrote:
> > I am having a problem in restoring from WAL files. I have restored
> > from a dump file and trying to step through the WAL files.
>
> > PANIC: syntax error in
On Sat, 2007-06-02 at 01:07 +0100, Jon Colverson wrote:
> Simon Riggs wrote:
> > I've spent some time re-examining the code and I can't see a route for
> > the discussed problem to occur. All the main code paths do not exhibit
> > this problem in 8.2, so I&#
w feature in 8,3), but
the disk failure has meant stuff you thought was on disk wasn't really.
So your DB has holes in it and you need to recover/failover/pull-hair.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
hive messages.
But it seems like you should be able to do
ls -l /var/lib/pgsql/bkp/myfile
to check your archive_command has succeeded, using your example
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end
e? Benchmark ? Availability ? Architecture ?
> Limitation : users, volumes ? Resouces needed ? Support ?
I would suggest you make your comparison based upon your specific needs,
not a purely abstract comparison. If your not sure what your
requirements are, research those first.
--
itself already undergone a PITR.
Have a look at pg_standby, accessible via CVS in contrib/pg_standby.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
med the primary role? (i.e.
> standby server goes *live*, and is subsequently restarted in the recovery
> mode).
No, not needed.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2
On Fri, 2007-06-29 at 10:52 -0400, Tom Lane wrote:
> "Simon Riggs" <[EMAIL PROTECTED]> writes:
> > Just ignore 0001. Recovery will work fine even if absent. Don't
> > ignore all history files though, just that one. Hmmm, come to think of
> > it, why
On Fri, 2007-07-20 at 14:19 -0400, Mark Steben wrote:
> We are currently at version 7.4.5.
You should upgrade if you want better performance and scalability.
Or maybe you should just use COPY?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end
ou need to use xlogdump
to locate the time of the last commit/abort record.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
restart point at %X/%X",
rmid,
checkPoint->redo.xlogid,
checkPoint->redo.xrecoff)));
to help trace such things in future.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
On Tue, 2007-08-28 at 18:49 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Yeh, we traced a problem with GIN indexes to this cause in early June;
> > Teodor fixed it quickly in REL8_2_STABLE, but that won't be available
> > until 8.2.5.
&
y. (pgsql-patches, 8
June). That one really needs to be in 8.3 - more review work, sorry.
Whatever we do, there's more docs coming on this for 8.3, pg_standby,
pg_compresslog and a few other points. Give me a week or so please.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
m disk after second, third and so on runs. Isn't is
> wrong that RDBMS tries to cache table data blocks at least PARTIALLY
> in the case of insufficient cache buffer?
It does cache partially, but its always the wrong part of the table.
BTQ, Oracle does that too...
--
Simon Riggs
stgres/archive/procuracion/00010018009D"
> "pg_xlog/RECOVERYXLOG"
Then we restart recovery from the last restartpoint.
Is that what you meant?
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)--
point WAL record that we find after checkpoint_timeout
seconds.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
On Thu, 2007-10-04 at 20:02 -0600, Benjamin Krajmalnik wrote:
> Is there a way to execute an external program from within a stored
> procedure?
Write a Function in C
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of bro
On Wed, 2007-10-10 at 11:46 -0500, Scott Whitney wrote:
> Is rsync a supported method for a warm standby server? Specifically, I'm
> thinking about:
> http://www.taygeta.com/ha-postgresql.html
That's dated 2001...
--
Simon Riggs
2ndQuadrant http://
way to do it?
> > 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
PITR facilities for
making a standalone backup.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
ably
good for peace of mind too, but it's a long way from being an essential
requirement.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
The design of the PITR system allows a product-agnostic backup. Anything
that can backup a file can backup PostgreSQL. There is no need for
special certifications of hologram logos.
You may need to write a few lines of script to do it, but that's not a
problem surely?
So you can use pg_dump or
and new data would be inaccessible.
As far as I am concerned, if any Postgres user loses data then we're all
responsible.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Thu, 2008-01-31 at 12:09 -0300, Alvaro Herrera wrote:
> > Simon Riggs wrote:
>
> >> As far as I am concerned, if any Postgres user loses data then we're all
> >> responsible.
>
> Remember, our license says this software is given without any warranty
>
On Thu, 2008-01-31 at 10:02 -0500, Chander Ganesan wrote:
> Magnus Hagander wrote:
> > On Thu, Jan 31, 2008 at 03:34:05PM +0100, Martijn van Oosterhout wrote:
> >
> >> On Thu, Jan 31, 2008 at 01:28:48PM +, Simon Riggs wrote:
> >>
> >>> That
cted the manual, but old emails stay
the same. We can also change the manual some more in response to
clarifications.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
when and why this happened, then either correct
the problem or report the bug.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
...
> <2008-02-25 07:15:56 CST >LOG: could not truncate directory
> "pg_multixact/members": apparent wraparound
Some interesting failures there.
Is this a modified Postgres server? Are you running externally supplied
C language functions? Have you had hardware p
oblem?
> HELP!!!
It is possible to recover some data in most situations, but it can take
anywhere from a day or two. My company offers database recovery
services, if you're willing to pay.
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
PostgreSQL UK 2008 Conference: http://www
about would be:
* What workloads are you running?
* What hardware will it run on?
* What performance is required?
...
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
PostgreSQL UK 2008 Conference: http://www.postgresql.org.uk
--
Sent via pgsql-admin mailing list (pgsql-admi
here a backup_label file as part of the tar?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
On Fri, 2008-05-16 at 13:21 -0400, Mark Steben wrote:
> Simon, I think you uncovered the problem but I don't see anyway around
> it Short of reloading the db from a pg_dump backup. Any suggestions
> would Be appreciated. Thanks,
Re-run the backup? Sounds safest.
--
Simon Riggs
ng not mentioned there we will update them.
Thanks,
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
do this by installing 3 separate postmasters on this machine?
> Obviously, if 2 went down at the same time, I'd have to do some magic to
> bring up another machine, but I'm not sure that's a concern.
Yes, that will work.
--
Simon Riggs www.2ndQuadrant.com
PostgreS
On Thu, 2008-06-26 at 13:01 -0500, Scott Whitney wrote:
> A 2nd question: Is it possible to have 2 standby servers with a single
> master duplicating to standby1 (at my coloc), and standby2 (at my office)?
> Assume no auto-failover.
Yes, that works too.
--
Simon Riggs
unt
> it might be wise to stop and restart the slave postmaster. Forward
> should be no problem though.
Yeh, you're good.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
On Fri, 2008-08-15 at 09:44 -0400, Carol Walter wrote:
> All the documentation I've read says that for Unix installations
> should compile source.
You're right. We should fix that so it also describes using pre-packaged
options also.
--
Simon Riggs www.2ndQuadrant
> I found this on the forums. Could it be the source of the problem I'm
> experiencing?
The way you are using this looks correct.
The startup process would not/should not fail in this way and there
should be additional messages between the log entries from 23:03 to
23:07. I don't
ckup product.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
, I thought you were looking after that build. If it's not being
> maintained, we'll need to remove it from the download pages unless
> someone else can volunteer?
I'll look at doing that. We need the SUSE builds also.
--
Simon Riggs www.2ndQuadrant.com
Postgr
On Tue, 2008-09-23 at 10:05 +0100, Dave Page wrote:
> On Tue, Sep 23, 2008 at 9:49 AM, Simon Riggs <[EMAIL PROTECTED]> wrote:
>
> >> Oh, I thought you were looking after that build. If it's not being
> >> maintained, we'll need to remove it from the dow
On Tue, 2008-09-23 at 21:05 +0300, Devrim GÜNDÜZ wrote:
> Hi,
>
> On Tue, 2008-09-23 at 09:49 +0100, Simon Riggs wrote:
> > I'll look at doing that. We need the SUSE builds also.
>
> I actually built 8.3.4 on SLES 10.2 on..err..Friday, while building
> Fedora/R
So if you trust crash recovery you should trust archive recovery, which
means WAL shipping. The differences are all about where you start and
stop WAL replay.
The second is that any form of replication requires testing.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Serv
t; it.
Please test the Hot Standby patch...
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
.3 docs have the wording
"A working example of a waiting restore_command is provided as a contrib
module named pg_standby. It should be used as a reference on how to
correctly implement the logic described above. It can also be extended
as needed to support specific configurations or environmen
o be at least twice as
fast on a 2+ CPU system.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
basically useless.
They are still better than nothing at all. I haven't read the whole
thread, but suggesting deleting things like that makes me go all
twitchy. :-). Do a couple of proper backups and then delete em.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Serv
RECOVERYHISTORY" which points to the
> following missing file "/WAL_ARCHIVE_DIR/0001.history"
>
> i wonder if it is fatal or not?
That's normal.
> I will not to start the process ot making the base backup and send it
> to my warm standby server. My warm stan
in future don't delete WAL files that may be
needed for recovery.
You can use
pg_controldata test | grep REDO | cut -d: -f 2
to find out the LSN of the last restartpoint, which can then be
converted into an xlogfilename using pg_xlogfile_name().
--
Simon Riggs www.2ndQuadrant.com
nia, and lay it down there. Simple enough but the time to travel
> > Over the network becomes an issue - 12 - 13 hours at best.
> > If we have to do this then we will. I just want to make sure I'm
> > understanding your advice.
>
> Yes.
Yes, but use rsync, so
not
> fail.
Seems like the stats files are changing while being copied.
I'd suggest excluding global/pgstat* from the backup.
Stats are reset at recovery anyway, so you've lost nothing.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
S
e. And it would appear that paragraph is in direct
conflict with paragraph (1) of same article.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscript
code hooks required to do this, if people want to contact me
off-list.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
a/pgsql/wals/alerts_oamp %f %p %r >>
> /home/postgresql/log/alerts_oamp/recovery.log'
You've set archive_timeout?
http://developer.postgresql.org/pgdocs/postgres/runtime-config-wal.html#RUNTIME-CONFIG-WAL-ARCHIVING
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Trainin
On Wed, 2009-03-04 at 15:37 -0500, Tom Lane wrote:
> Simon Riggs writes:
> > On Wed, 2009-03-04 at 15:59 +0200, Peter Eisentraut wrote:
> >> samana srikanth wrote:
> >>> Can we do a point-in-time restore of a single database out of n
> >>> databases??.
On Wed, 2009-03-04 at 16:27 -0500, Tom Lane wrote:
> Simon Riggs writes:
> > On Wed, 2009-03-04 at 15:37 -0500, Tom Lane wrote:
> >> It's not as easy as all that. What will you do with updates to shared
> >> catalogs?
>
> > Apply them.
>
> ... wh
ithout
> breaking the other databases that are already in it". There is zero
> chance of ever doing that with a WAL-based backup --- transaction ID
> inconsistencies would break it, even without considering the contents
> of shared catalogs.
Agreed.
--
Simon Riggs www.2n
orage
>
> Any suggestion and recommendation are welcome.
Postgres has sophisticated techniques for backup and recovery, proven in
the field over many years.
Please start here
http://developer.postgresql.org/pgdocs/postgres/backup.html
Integration is possible with 3rd party devices and
of experience with helping people out with
problems like this, including data recovery from damaged databases.
Please let us know if we can be of any help. Apologies for mentioning
commercial matters on list, though this work helps fund further
developments in this area.
--
Simon Riggs www.2nd
PARED or ROLLBACK PREPARED on a session *after* issuing a PREPARE
TRANSACTION then it should give an ERROR. If the session continues to
exist then the server has not crashed and so it must always be
programming error.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Suppo
y during
> the time B is down: I'm only stopping/restarting PostgreSQL, not the entire
> machine.)
Recovery is restartable. Not quite from where it left off, but near
enough that it won't take too long to get back to where it left off.
--
Simon Riggs www.2ndQuadrant.
ndexdb, clusterdb or any custom written jobs.
You need to break out your top few tables into separate jobs, e.g.
vacuumdb -t big1
vacuumdb -t big2
...
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subs
do "INSERT INTO pg_autovacuum" (or ALTER TABLE/SET in 8.4)
> just after you've created the table.
This doesn't work with vacuumdb, only with autovacuum.
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make c
On Thu, 2009-10-15 at 09:24 -0300, Alvaro Herrera wrote:
> Simon Riggs escribió:
> > On Wed, 2009-10-14 at 13:57 -0300, Alvaro Herrera wrote:
> > > Anj Adu escribió:
> > >
> > > > I have several "daily" tables that get dropped every day..Is there a
an integrated and
fully-supported option with Postgres. You will need additional
non-volatile cache on your disks to ensure that is a safe option, though
that will yield performance advantages also.
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mailing list (pgsql-admi
On Mon, 2010-03-15 at 11:27 +0200, Nicos Panayides wrote:
> thanks for the suggestion. What kind of space savings should I expected
> from turning off full_page_writes?
Substantial, though you should measure it and see, since it is workload
dependent.
--
Simon Riggs
ng a bug, or not.
The manual describes what is happening:
http://developer.postgresql.org/pgdocs/postgres/continuous-archiving.html#BACKUP-BASE-BACKUP
Step 5
Is there anything you think should be added to the manual?
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mai
for performance reasons, or is auto-vac
> sufficient?
If you don't know why you are running it, then you should skip it and
measure the difference.
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to
ing, but apart from those
the load is actually very low in normal running.
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
copied in on mails so that I can see the issues exist. I do not
promise to respond to every mail I'm copied on, though, but it at least
helps me manage the fire hydrant.
Thanks!
--
Simon Riggs www.2ndQuadrant.com
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.or
of
> a hot standby installation, if that matters.
Have you ever performed a switchover operation? If you've never run an
extended recovery on that server, its less likely to be anything HS
related.
Are you running any special hot standby parameters?
--
Simon Riggs www.2ndQuadrant.com
quot;%f"'
># command to use to archive a logfile segment
> archive_timeout = 3600 # force a logfile segment switch after
> this
> hot_standby = off # allows queries during recovery
> max_wal_senders = 3 # max number of walsender processes
> wa
replication/table
> space layout/performance tunning etc.
2ndQuadrant provides all of these services. Be happy to hear from you.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent via pgsql-admin mailing list (pgsql-admin@pos
>
> DO you have some suggestion for our implementaiont if exists??
PostgreSQL 9.0 is production ready now and supports Hot Standby, which
is exactly what you want.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Training and Services
--
Sent
ecord, playing with pg_clog files like this is an
insanely unsafe thing to do. Notably it will make all aborted
transactions in that range become committed, leading to all sorts of
fun.
This is a desperate measures only action and not one that looks
immediately related to the problem.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
tgresql/9.0/data/trigger'
> standby_mode = 'on'
> primary_conninfo = 'host=10.5.17.40 port=5432 user=postgres'
>
> thanks for any input.
That all looks normal to me, as far as I can tell.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
No, you can't.
Sequences cache their values for performance. Any crash or failover
will produce the same effect.
We might change that for switchovers but it would take some effort and
would still be the same if it crashes.
--
Simon Riggs http://www.2ndQuadrant.com/
Po
1 - 100 of 225 matches
Mail list logo
