On Fri, Oct 14, 2016 at 11:27 PM, Albe Laurenz wrote:
> After a successful commit, the WAL file and its metadata are on disk.
> Moreover, the file metadata won't change (except for the write and access
> timestamps) because WAL files are created with their full size and
Thanks Rakesh.
Let me explain my reason to have a replica server.
We run odoo server 7.x with ubuntu 14.
But we are working on a BI system right now(Pentaho), them we want to
run those heavy reports on the replica and let the current production
system on the master.
This is why I was thinking
>Other thing, with bucardo what is the difference between in a
>master-master replica vs master-slave, at the end in both ways the
>user has a 2nd DB with R/W permission?
I think in a M-M mode, updates from both dbs will be replicated to the other db.
In other words they will be eventually
Thanks Rosser for your answer.
Other thing, with bucardo what is the difference between in a
master-master replica vs master-slave, at the end in both ways the
user has a 2nd DB with R/W permission?
Thanks.
On Thu, Oct 13, 2016 at 9:40 PM, Rosser Schwarz
wrote:
> On
Hi,
Personally where possible I would always internal features of any DB engine.
These are pre-compiled, tested for performance and are ingrained into the
system. So they can naturally be expected to be slightly faster than even
triggers. In the case of your question, why not use serial
On Fri, Oct 14, 2016 at 7:12 AM, Арсен Арутюнян wrote:
> Hi, everyone!
>
> I have a table:
>
> create table testpr(id serial,priority integer,unique(priority) DEFERRABLE,
> primary key(id));
>
This:
> and a trigger which, when added to this table, automatically sets priority
> as
Hi, everyone!
I have a table:
create table testpr(id serial,priority integer,unique(priority) DEFERRABLE,
primary key(id));
and a trigger which, when added to this table, automatically sets priority as
the maximum value +1
CREATE OR REPLACE FUNCTION PriorityCheck() RETURNS trigger AS $$
BEGIN
t.dalpo...@gmail.com wrote:
> 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
On Thu, Oct 13, 2016 at 5:26 PM, Thomas Munro
wrote:
> On Fri, Oct 14, 2016 at 2:04 AM, Kevin Grittner wrote:
>> Where do you see a problem if REPEATABLE READ handles INSERT/ON
>> CONFLICT without error?
> I think the ON CONFLICT
> equivalent
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
NVM, I guess that I just didn't wait long enough for the re-index operation
to complete... We're good now...
On Fri, Oct 14, 2016 at 6:45 AM, Deven Phillips
wrote:
> Here's hoping someone can help me... Overnight, our primary database
> server (part of a master/slave
Here's hoping someone can help me... Overnight, our primary database server
(part of a master/slave replication pair) ran out of disk space. I have
cleaned up space now, but while performing some VACUUM ANALYZE commands I
find that there is some corruption.
I'm getting messages like: ERROR:
Thanks for the suggestion, Used || , actually I was reluctant to use this
because my columns could have contained null values. But that I have handled
using COALESCE.
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, October 13, 2016 7:37 PM
To: Jaisingkar,
13 matches
Mail list logo