Re: PostgreSQL Developer Best Practices - Mailing list pgsql-general

From Karsten Hilbert
Subject Re: PostgreSQL Developer Best Practices
Date
Msg-id trinity-a020d60a-2532-4737-8ba5-f88d335f0290-1440527894237@3capp-gmx-bs21
Whole thread Raw
In response to Re: PostgreSQL Developer Best Practices  (Neil Tiffin <neilt@neiltiffin.com>)
Responses Re: PostgreSQL Developer Best Practices
List pgsql-general
> In most cases developers don’t care about index, unique, foreign key, or primary key names (from a coding standpoint)

Until the day they'd like to write a reliable database change script.

(PG's internal conventions for object names _have_ changed over the years)

Karsten


pgsql-general by date:

Previous
From: David Kerr
Date:
Subject: Re: Why does splitting $PGDATA and xlog yield a performance benefit?
Next
From: Gavin Flower
Date:
Subject: Re: Why does splitting $PGDATA and xlog yield a performance benefit?