-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
- --On Wednesday, August 15, 2007 20:57:14 +0200 Magnus Hagander <[EMAIL PROTECTED]> wrote: > Marc G. Fournier wrote: >> >> >> --On Wednesday, August 15, 2007 12:11:35 +0200 Peter Eisentraut >> <[EMAIL PROTECTED]> wrote: >> >>> Am Mittwoch, 15. August 2007 04:20 schrieb Tom Lane: >>>> we should at least log such commands, and maybe disallow to anyone >>>> except Marc's "pgsql" account. >>> I don't think we should disallow it. Or otherwise we might one day be stuck >>> if we need to release while some specific person is on vacation. >> >> This isn't a big issue ... note that the 'restriction' is easy to remove >> ... you checkout CVSROOT, modify taginfo and comment out the ALL l ine and >> check that in ... >> >> What this will prevent is an 'accidental tagging' ... you would have to >> consciously remove the restriction .. but its something anyone could do ... >> >>> I never understood why tagging uses a special account anyway. It should be >>> done as the person doing the tagging. >> >> Agreed, I'm going to start doing it as myself from now on ... I'm not even >> 100% certain *why* I started doing it as pgsql in the first place ... > > If you're doing that, we should probably just delete the pgsql userid > from the system? Or at least change it so it doesn't have 'dev' > permissions. That way you can't do it wrong in that direction ;-) > Seems reasonable? there is no pgsql user *on* cvs.postgresql.org, at least there wasn't when I logged on last night: cvs# grep pgsql /etc/passwd cvs# - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFGw1AR4QvfyHIvDvMRArsSAJ9WzXyMu7Io6dP8kDnR5HHex1f1gQCg7iDq 3p2RrAzww4dCDPVCyMozAnM= =L+/M -----END PGP SIGNATURE----- ---------------------------(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
