Il 12/12/2016 02:42, David G. Johnston ha scritto:
On Saturday, December 10, 2016, Tom DalPozzo mailto:t.dalpo...@gmail.com>> wrote:
I have one direct DB client (let's name it MIDAPP) only. This
client of the DB is a server for up to 1 final clients.
Any time M
Il 25/10/2016 18:17, Francisco Olarte ha scritto:
I may be confused but...
On Tue, Oct 25, 2016 at 5:08 PM, t.dalpo...@gmail.com
wrote:
These servers are configured for Sync streaming replication .
Let's suppose that the standby stays down for a long time, then it restarts,
Doesn't s
Hi,
let's suppose I have:
- a primary server with its own local archive location, configured for
continuous archiving
- a standby server without archive.
These servers are configured for Sync streaming replication .
Let's suppose that the standby stays down for a long time, then it
restarts,
So, as for the data content of the WAL file, I see that no more page
will be allocated. I wonder if during a crash, strange things can still
happen at disk level however, in particular in SSD devices; on these
things we have no control, and perhaps journaling helps?
As for the metadata, if durin
Hi,
I've a very huge table whose 1st column is a numeric value, starting
from 0 at the 1st row and incremented by 1 each new row I inserted.
No holes, no duplicates.
I need to perform some very fast query based on this value, mainly
around the last inserted rows.
What is the best I can do? A no
Hi,
two question related to the WAL.
1) I read in the doc that journaled FS is not important as WAL is
journaling itself. But who garantees that the WAL is written correctly?
I know that it's sequential and a partial update of WAL can be discarded
after a restart. But am I sure that without
