Re: Re: logical changeset generation v3 - comparison to Postgres-R change set format

Dimitri Fontaine <dimitri@2ndquadrant.fr>

From: Dimitri Fontaine <dimitri@2ndQuadrant.fr>
To: Hannu Krosing <hannu@2ndQuadrant.com>
Cc: Noah Misch <noah@leadboat.com>, Markus Wanner <markus@bluegap.ch>, Andres Freund <andres@anarazel.de>, pgsql-hackers@postgresql.org
Date: 2013-01-13T20:06:21Z
Lists: pgsql-hackers
Hannu Krosing <hannu@2ndQuadrant.com> writes:
>> Does this hint that postgreSQL also needs an sameness operator
>> ( "is" or "===" in same languages).
>
> How do people feel about adding a real sameness operator ?

Well. I would prefer it if we can bypass the need for it.

Then Do we need the full range of eq, eql, equal and equalp predicates,
and would all of them allow overriding or just some?

  http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node74.html

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Background worker processes

  2. Rearrange storage of data in xl_running_xacts.

  3. Basic binary heap implementation.

  4. Embedded list interface

  5. Refactor xlog.c to create src/backend/postmaster/startup.c