Launchpad should run with standard_conforming_strings=on in postgresql.conf

Bug #90809 reported by Stuart Bishop on 2007-03-09
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
William Grant

Bug Description

We will have trouble with future PostgreSQL upgrades if we continue to send non-SQL standard escaped strings. Most of this should be fixed by upgrading to psycopg2.

Related branches

Stuart Bishop (stub) on 2007-03-09
Changed in launchpad:
status: Unconfirmed → Confirmed
importance: Undecided → Medium
Robert Collins (lifeless) wrote :

Where are we at on this?

Changed in launchpad:
importance: Medium → High
assignee: nobody → Stuart Bishop (stub)
Stuart Bishop (stub) on 2011-12-19
tags: added: pg9
Stuart Bishop (stub) on 2011-12-19
Changed in launchpad:
importance: High → Low
Stuart Bishop (stub) on 2012-02-03
tags: removed: pg9
tags: added: pg9
Stuart Bishop (stub) wrote :

I was going to do this as part of the pg 9 migration, but there is quite a bit of fallout. We will deal with standard_confirming_strings separately, so any fallout from pg 9 or standard_confirming_strings is correctly attributed.

There are two major areas I've seen where we expect plain quoted strings to accept backslash quoting:
 - regular expressions
 - accidental binary -> text casting. In particular, byte strings passed to Storm are sent as binary and at some point this is being reassembled to text. We should be passing Unicode, but we don't notice.

William Grant (wgrant) on 2015-02-19
Changed in launchpad:
assignee: Stuart Bishop (stub) → William Grant (wgrant)
status: Triaged → In Progress
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
William Grant (wgrant) on 2015-03-06
tags: added: qa-ok
removed: qa-needstesting
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers