Re: VALID UNTIL - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: VALID UNTIL
Date
Msg-id CAFcNs+piQYqCkOy=YXstxca9G_zeOUwRmy-V_C8Dgk1-crS82A@mail.gmail.com
Whole thread Raw
In response to Re: VALID UNTIL  (David Fetter <david@fetter.org>)
Responses Re: VALID UNTIL  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

2012/3/14 David Fetter <david@fetter.org>

I don't know how frequently people use VALID UNTIL, but I'm guessing
it's not terribly often because yours is the first comment about how
it's not exposed, so I'd tend toward putting it in attributes rather
than a separate column.


The attached patch put VALID UNTIL into attributes column in verbose mode like example above.

bdteste=# \du
                             List of roles
 Role name |                   Attributes                   | Member of 
-----------+------------------------------------------------+-----------
 bucardo   | Superuser, Create role, Create DB, Replication | {}
 postgres  | Superuser, Create role, Create DB, Replication | {}

bdteste=# \du+
                                                          List of roles
 Role name |                                        Attributes                                         | Member of | Description  
-----------+-------------------------------------------------------------------------------------------+-----------+--------------
 bucardo   | Superuser, Create role, Create DB, Valid until 2012-12-31 23:59:59.999999-02, Replication | {}        | bucardo role
 postgres  | Superuser, Create role, Create DB, Replication                                            | {}        | 


Regards,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Blog sobre TI: http://fabriziomello.blogspot.com

Attachment

pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: Faster compression, again
Next
From: Tatsuo Ishii
Date:
Subject: Re: Too many IO?