Re: pgsql: Update why unified diff is _sometimes_ better. - Mailing list pgsql-committers

From Andrew Dunstan
Subject Re: pgsql: Update why unified diff is _sometimes_ better.
Date
Msg-id 43AD9C19.2040309@dunslane.net
Whole thread Raw
In response to pgsql: Update why unified diff is _sometimes_ better.  (momjian@postgresql.org (Bruce Momjian))
Responses Re: pgsql: Update why unified diff is _sometimes_ better.
List pgsql-committers
spelling error: s/surrouding/surrounding/


cheers

andrew



Bruce Momjian wrote:

>Log Message:
>-----------
>Update why unified diff is _sometimes_ better.
>
>Modified Files:
>--------------
>    pgsql/doc:
>        FAQ_DEV (r1.102 -> r1.103)
>        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/FAQ_DEV.diff?r1=1.102&r2=1.103)
>    pgsql/doc/src/FAQ:
>        FAQ_DEV.html (r1.105 -> r1.106)
>        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/FAQ_DEV.html.diff?r1=1.105&r2=1.106)
>
>---------------------------(end of broadcast)---------------------------
>TIP 9: In versions below 8.0, the planner will ignore your desire to
>       choose an index scan if your joining column's datatypes do not
>       match
>
>
>

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update why unified diff is _sometimes_ better.
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Spell fix.