Set server behaviors on a per-session basis?

From: Ken Johanson <pg-user(at)kensystem(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Set server behaviors on a per-session basis?
Date: 2008-02-04 06:26:23
Message-ID: 47A6B00F.6030405@kensystem.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

(re-post, last seemed not to get on-list)

Hi all,

In the link below we asked if it was possible to set, in this case, the
standard_conforming_strings behavior, on a per-connection basis.

http://www.grokbase.com/topic/2006/07/27/backslash-as-ordinary-char-vs-not-set-via-a-connection-session-variable/PwunvQ3dQxAVOpprZ606aKELsYU

The responses were good to see -- the ability to set it on a role or
database context is great.. however in some hosting / shared
environments, one-role per behavior isn't always practical, even though
it's arguably the ideal approach.

A first question: will the current server design easily allow some
change that lets us set behaviors (like standard_conforming_strings) on
a per-connection basis? Or are per-connection behaviors a substantial
rework?

A second question: is support for a general notion of "behavior" on the
roadmap for any of the three contexts (roles, database, sessions)? Not
just standard_conforming_strings, but both conformant and non behaviors.
Say accepting relaxed typing (quoted ints etc), implicit AS-keyword in
SELECT lists (someday and in sacrifice of regclass), etc. Even to allow
newer PGs to behave as old ones.

These two features would ease migration *from* non-compliant/3rd party
DBs -- and also to ease PG itself *into* standard-compliant modes (e.g
'implicit AS-keyword in SELECT lists'). Also may allow some blackbox
apps to migrate from 3rd party DBs.

-Ken

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2008-02-04 06:30:41 Re: PostgreSQL Certification
Previous Message Joshua D. Drake 2008-02-04 05:55:46 Re: [Cert] Re: PostgreSQL Certification