Re: Changeset Extraction v7.3 - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: Changeset Extraction v7.3
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17C9F44C@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: Changeset Extraction v7.3  (Andreas Karlsson <andreas@proxel.se>)
Responses Re: Changeset Extraction v7.3  (Christian Convey <christian.convey@gmail.com>)
List pgsql-hackers
Andreas Karlsson wrote:
> On 01/28/2014 10:56 PM, Andres Freund wrote:
>> On 2014-01-28 21:48:09 +0000, Thom Brown wrote:
>>> On 28 January 2014 21:37, Robert Haas <robertmhaas@gmail.com> wrote:
>>>> On Tue, Jan 28, 2014 at 11:53 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>>>> The point of Andres's patch set is to introduce a new technology
>>>> called logical decoding; that is, the ability to get a replication
>>>> stream that is based on changes to tuples rather than changes to
>>>> blocks.  It could also be called logical replication.  In these
>>>> patches, our existing replication is referred to as "physical"
>>>> replication, which sounds kind of funny to me.  Anyone have another
>>>> suggestion?
>>>
>>> Logical and Binary replication?
>>
>> Unfortunately changeset extraction output's can be binary data...
> 
> I think "physical" and "logical" are fine and they seem to be well known
> terminology. Oracle uses those words and I have also seen many places
> use "physical backup" and "logical backup", for example on Barman's
> homepage.

+1

I think it also fits well with the well-known terms "physical [database]
design" and "logical design".  Not that it is the same thing, but I
believe that every database person, when faced with the distiction
"physical" versus "logical", will conclude that the former refers to
data placement or block structure, while the latter refers to the
semantics of the data being stored.

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: Add min and max execute statement time in pg_stat_statement
Next
From: Craig Ringer
Date:
Subject: Re: WIP patch (v2) for updatable security barrier views