Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 7
Impact
~9k people reached

  • 0 posts edited
  • 0 helpful flags
  • 1 vote cast
Feb
18
comment Can't promote PostgreSQL warm standby server to start serving data
The restore_command can be like this: restore_command = ‘cp /var/lib/pgsql/9.4/archive/%f %p’
Feb
17
comment Can't promote PostgreSQL warm standby server to start serving data
Just a comment: the recovery.conf generated includes a primary_conninfo parameter. So, this means streaming replication is enabled. If I don't want streaming replication, I should use restore_command instead.
Feb
17
answered Can't promote PostgreSQL warm standby server to start serving data
Feb
17
asked Can't promote PostgreSQL warm standby server to start serving data
Feb
25
awarded  Notable Question
Apr
4
awarded  Scholar
Apr
4
accepted MySQL: Loop over cursor results ends ahead of schedule
Apr
4
awarded  Popular Question
Mar
15
awarded  Autobiographer
Aug
29
comment memc_delete called from a MySQL trigger loop fails randomly
Mmmm, I don't think so. This trigger is raised after update on one table. I execute 'UPDATE' over this table and then the trigger is executed. That's all. Any the MySQL log doesn't show more activity.
Aug
29
asked memc_delete called from a MySQL trigger loop fails randomly
Aug
23
awarded  Student
Aug
23
awarded  Teacher
Aug
23
answered MySQL: Loop over cursor results ends ahead of schedule
Aug
23
comment MySQL: Loop over cursor results ends ahead of schedule
Oh, sorry. The 'after delete' trigger is executed over one table different from the table in which I execute the 'update'/'delete' operations. Already edited that.
Aug
23
awarded  Supporter
Aug
23
revised MySQL: Loop over cursor results ends ahead of schedule
Minor bug in psc fixed.
Aug
22
awarded  Editor
Aug
22
comment MySQL: Loop over cursor results ends ahead of schedule
I've included it, cutting the irrelevant parts.
Aug
22
revised MySQL: Loop over cursor results ends ahead of schedule
Added some SQL code to clarify the question.