pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Upgrading PostgreSQL to 7.1.3
4+ messages / 3 participants
[nested] [flat]

* Upgrading PostgreSQL to 7.1.3
@ 2002-04-02 12:13  Gordon Clarke <gordonc@adf-serials.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Gordon Clarke @ 2002-04-02 12:13 UTC (permalink / raw)
  To: pgsql-sql

Hi All,

At our community radio station we just upgraded from v7.0.2 to 7.1.3 and
quite a few things have changed which has caused the following questions.

1. When one does a \d on a table the type description for a varchar field
has changed from 
	varchar(40)
to
	character varying(40)
which is most annoying as it forces lines to wrap because of long text in
the modifier section.

Can this be set back to the former? If so how is it done?

2. Previously when issuing a \z command it listed in the 'access
permission' just the public and group permissions, eg.
annoucr        | {"=r","group admin=arwR","group music_coord=r"}

Now it includes the owner name as well as all its permissions eg.
annoucr        | {"=r","zedadmin=arwR","group admin=arwR","group
music_coord=r"}

Again this is annoying because of wrapping. Further it shows the
permissions of the owner for tables which we don't want people to know
about and have them try and connect to. Can this option be switched off
and hence returned to the previous format?

3. Previously the permissions on a sequence were just read-only to PUBLIC
(ie. {"=r"}) which allowed any of our applications to access the sequence
if it needed to. Now it appears that the permissions are to be allocated
to the group accessing the application and that it must be read-write. 

Isn't this a security issue? Now anyone (in the group) can write to the
sequence and update it and not just the owner of the sequence. Can someone
explain for me the reason for this change? Tom?

I don't want this to sound negative as there are many good and welcome
enhancements in v7.1.3. Keep up the good work chaps.

Mind u I haven't had a look at all the new features yet so hopefully there
wont be too many more surprises. :)

-- 
Cheers...Gordon
-------------+------------------------------------------------------------
ADF Aircraft | Cataloguing the serial numbers of Australian Defence Force
   Serial    |            aircraft for all the three series.
  Numbers    |               http://www.adf-serials.com
-------------+------------------------------------------------------------





^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Upgrading PostgreSQL to 7.1.3
@ 2002-04-03 01:41  Peter Eisentraut <peter_e@gmx.net>
  parent: Gordon Clarke <gordonc@adf-serials.com>
  0 siblings, 1 reply; 4+ messages in thread

From: Peter Eisentraut @ 2002-04-03 01:41 UTC (permalink / raw)
  To: Gordon Clarke <gordonc@adf-serials.com>; +Cc: pgsql-sql

Gordon Clarke writes:

> At our community radio station we just upgraded from v7.0.2 to 7.1.3 and
> quite a few things have changed which has caused the following questions.
>
> 1. When one does a \d on a table the type description for a varchar field
> has changed from
> 	varchar(40)
> to
> 	character varying(40)
> which is most annoying as it forces lines to wrap because of long text in
> the modifier section.
>
> Can this be set back to the former? If so how is it done?

Not without editing the source code.

> 2. Previously when issuing a \z command it listed in the 'access
> permission' just the public and group permissions, eg.
> annoucr        | {"=r","group admin=arwR","group music_coord=r"}
>
> Now it includes the owner name as well as all its permissions eg.
> annoucr        | {"=r","zedadmin=arwR","group admin=arwR","group
> music_coord=r"}

If the owner has some permissions they need to be stored somewhere.  This
was actually part of a bug fix -- in the 7.0 case the owner actually
didn't have any permissions -- so it won't change.

> 3. Previously the permissions on a sequence were just read-only to PUBLIC
> (ie. {"=r"}) which allowed any of our applications to access the sequence
> if it needed to. Now it appears that the permissions are to be allocated
> to the group accessing the application and that it must be read-write.

The reason that you need write access is that if you call nextval you
actually write to the sequence.  If you call currval you don't need write
access.

-- 
Peter Eisentraut   peter_e@gmx.net




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Upgrading PostgreSQL to 7.1.3
@ 2002-04-24 05:30  Rajesh Kumar Mallah <mallah@trade-india.com>
  parent: Peter Eisentraut <peter_e@gmx.net>
  0 siblings, 1 reply; 4+ messages in thread

From: Rajesh Kumar Mallah @ 2002-04-24 05:30 UTC (permalink / raw)
  To: Peter Eisentraut <peter_e@gmx.net>; +Cc: Gordon Clarke <gordonc@adf-serials.com>; pgsql-sql

Hi ,

Any particular reson of not upgrading to 7.2.1 instead??

Peter Eisentraut wrote:

> Gordon Clarke writes:
>
> > At our community radio station we just upgraded from v7.0.2 to 7.1.3 and
> > quite a few things have changed which has caused the following questions.
> >
> > 1. When one does a \d on a table the type description for a varchar field
> > has changed from
> >       varchar(40)
> > to
> >       character varying(40)
> > which is most annoying as it forces lines to wrap because of long text in
> > the modifier section.
> >






^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Upgrading PostgreSQL to 7.1.3
@ 2002-04-28 05:24  Gordon Clarke <gordonc@adf-serials.com>
  parent: Rajesh Kumar Mallah <mallah@trade-india.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Gordon Clarke @ 2002-04-28 05:24 UTC (permalink / raw)
  To: Rajesh Kumar Mallah <mallah@trade-india.com>; +Cc: Peter Eisentraut <peter_e@gmx.net>; pgsql-sql

Hi Rajesh,

> Any particular reson of not upgrading to 7.2.1 instead??

Does this version reverse the changes I mentioned below that were
implemented in 7.1.3?
 
> Peter Eisentraut wrote:
> 
> > Gordon Clarke writes:
> >
> > > At our community radio station we just upgraded from v7.0.2 to 7.1.3 and
> > > quite a few things have changed which has caused the following questions.
> > >
> > > 1. When one does a \d on a table the type description for a varchar field
> > > has changed from
> > >       varchar(40)
> > > to
> > >       character varying(40)
> > > which is most annoying as it forces lines to wrap because of long text in
> > > the modifier section.
> > >
> 
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 

-- 

---
Cheers...Gordon
-------------+------------------------------------------------------------
ADF Aircraft | Cataloguing the serial numbers of Australian Defence Force
   Serial    |            aircraft for all the three series.
  Numbers    |               http://www.adf-serials.com
-------------+------------------------------------------------------------





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2002-04-28 05:24 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2002-04-02 12:13 Upgrading PostgreSQL to 7.1.3 Gordon Clarke <gordonc@adf-serials.com>
2002-04-03 01:41 ` Peter Eisentraut <peter_e@gmx.net>
2002-04-24 05:30   ` Rajesh Kumar Mallah <mallah@trade-india.com>
2002-04-28 05:24     ` Gordon Clarke <gordonc@adf-serials.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox