On Wed, Jul 8, 2015 at 03:10:46PM -0700, Josh Berkus wrote:
>
> > That note has been there forever, in particular since before we
> > supported CONCURRENTLY, which is pretty darn important in many uses
> > nowadays. Since it seems like some users have taken this suggestion
> > seriously, e.g. on
> That note has been there forever, in particular since before we
> supported CONCURRENTLY, which is pretty darn important in many uses
> nowadays. Since it seems like some users have taken this suggestion
> seriously, e.g. on stackoverflow[1], how about we remove this outdated
> suggestion? There
Hi,
I noticed that the note on a page about unique indexes
http://www.postgresql.org/docs/current/static/indexes-unique.html
says "The preferred way to add a unique constraint to a table is ALTER
TABLE ... ADD CONSTRAINT. The use of indexes to enforce unique constraints
could be considered an im
Alvaro Herrera <[EMAIL PROTECTED]> writes:
> On 4.1.2.1. String Constants, the following note appears:
> Note: While ordinary strings now support C-style backslash escapes,
> future versions will generate warnings for such usage and eventually
> treat backslashes as literal characters to be
On 4.1.2.1. String Constants, the following note appears:
Note: While ordinary strings now support C-style backslash escapes,
future versions will generate warnings for such usage and eventually
treat backslashes as literal characters to be standard-conforming.
That future version is 8.2,
