Hi. Is there any possibility for creating trigger file automatically in
postgres. Scenario is as follows :
There are some application which is having this postgres database. There are
main & backup database. Application is normally connected to first server.
If main server fails, application shoul
Alvaro Herrera writes:
> Yeah, maybe we should make it put the failed table at the end of the
> list, for the next run. This is not simple to implement, if only
> because autovac workers don't have any way to persist state from one run
> to the next. But this kind of thing causes enough problems
Excerpts from Kevin Grittner's message of jue may 13 10:25:04 -0400 2010:
> Ireneusz Pluta wrote:
>
> > many different autovacuums on the same table cycling in start-fail
> > scenario because of invalid page headers of some indexes of the
> > table. Manual VACUUM VERBOSE said me that, now I can
On Thu, May 13, 2010 at 8:15 PM, Jamie Tufnell wrote:
> Hi,
>
> We have a webapp backed by a single PostgreSQL server and I'd like to
> add a second primarily for availability. I figure if we can load
> balance reads too then why not.
>
> Having read over the HA docs/matrix, I'm considering using
Hi,
We have a webapp backed by a single PostgreSQL server and I'd like to
add a second primarily for availability. I figure if we can load
balance reads too then why not.
Having read over the HA docs/matrix, I'm considering using 9.0's hot
standby with pgpool-II to automatically balance reads wi
On Thu, May 13, 2010 at 5:11 PM, Plugge, Joe R. wrote:
> Nevermind ... I RTFM ...
>
> echo "alter table mytable ENABLE REPLICA TRIGGER check_lockout;" | psql
> mydb
>
This is not good idea. Always run DDL script using Slony execute script.
http://www.slony.info/documentation/ddlchanges.html
Nevermind ... I RTFM ...
echo "alter table mytable ENABLE REPLICA TRIGGER check_lockout;" | psql mydb
-Original Message-
From: pgsql-admin-ow...@postgresql.org
[mailto:pgsql-admin-ow...@postgresql.org] On Behalf Of Plugge, Joe R.
Sent: Thursday, May 13, 2010 4:02 PM
To: pgsql-admin@postg
Anyone know if it is possible to create an update trigger on the destination
side of a replicated table in Slony-I and have the replication itself cause the
trigger to fire? I was able to add the trigger but when run the test
transaction through, it does not seem to be firing. It works on the
On Thu, May 13, 2010 at 09:31:27AM -0500, Kevin Grittner wrote:
> Ray Stell wrote:
> > ,3440,,2010-05-13 09:06:35.734 EDT,4bebf95b.d70,5,2010-05-13
> > 09:06:35 EDT,0,FATAL: could not restore file "0002.history"
> > from archive: return code 32512
>
> Return code 32512? I think you'd be OK
Ray Stell wrote:
> ,3440,,2010-05-13 09:06:35.734 EDT,4bebf95b.d70,5,2010-05-13
> 09:06:35 EDT,0,FATAL: could not restore file "0002.history"
> from archive: return code 32512
Return code 32512? I think you'd be OK if your recovery script
returned 1 when it didn't find this file.
-Kevin
On Tue, May 11, 2010 at 04:29:18PM +0300, Devrim G?ND?Z wrote:
> On Tue, 2010-05-11 at 09:16 -0400, Ray Stell wrote:
> > What are the steps for upgrade of a primary/PITR standby pair to the
> > latest 8.3 patchset, 8.3.6-8.3.10? I don't see this in the docs.
> > Should there be something added t
Ireneusz Pluta wrote:
> many different autovacuums on the same table cycling in start-fail
> scenario because of invalid page headers of some indexes of the
> table. Manual VACUUM VERBOSE said me that, now I can also see that
> in related ERROR-CONTEXT log message pairs. I dropped the damaged
>
12 matches
Mail list logo
