On Thursday 19 January 2012, Jeremy Dunck wrote:
> There's a known problem w/ latest pg (2.4.2) and we decided not to
> backport the fix to 1.3.x because there's a workaround.
>
> https://code.djangoproject.com/ticket/16250
>
> All well and good, but someone coming to Django w/ postgres will
There's a known problem w/ latest pg (2.4.2) and we decided not to
backport the fix to 1.3.x because there's a workaround.
https://code.djangoproject.com/ticket/16250
All well and good, but someone coming to Django w/ postgres will have
a bad first-run experience because the docs don't mention
