--On Donnerstag, Februar 14, 2008 15:52:31 +1100 Brendan Jurd
[EMAIL PROTECTED] wrote:
Hello hackers,
psql's \du command currently does not list the INHERIT role attribute.
It does show the other privilege attributes (superuser, create role,
create db), and INHERIT seems like the kind of
Brendan Jurd escribió:
Hello hackers,
psql's \du command currently does not list the INHERIT role attribute.
It does show the other privilege attributes (superuser, create role,
create db), and INHERIT seems like the kind of thing a user
executing\du would want to know.
I'd like to add
On Thu, Feb 14, 2008 at 07:51:31AM +0100, Raphaël Jacquot wrote:
in fact, I got stuck in pl/pgsql with the fact that there's no way to
access the NEW tuple in an indirect way, having the name of the column
in some variable. (I found that it could be done in plperl, but that
left me with a
Paul van den Bogaard (Sun) suggested to me that we could use more than
two WAL locks to improve concurrency. I think its possible to introduce
such a scheme with some ease. All mods within xlog.c
The scheme below requires an extra LWlock per WAL buffer.
Locking within XLogInsert() would look
--On Donnerstag, Februar 14, 2008 10:27:37 -0300 Alvaro Herrera
[EMAIL PROTECTED] wrote:
I wonder if it's possible to create a more compact output -- say, a
fixed-width column, with a letter for each enabled attribute, or a space
in the respective position when the attribute is disabled.
Naz Gassiep [EMAIL PROTECTED] writes:
I think that it would be great if the pg_timezone_names and
pg_timezone_abbrevs included a boolean field indicating if that item is
in the Olsen DB
Huh? They're all in the Olsen DB.
regards, tom lane
=?UTF-8?B?UmFwaGHDq2wgSmFjcXVvdA==?= [EMAIL PROTECTED] writes:
so, I propose the use of
NEW[variable_containing_the_column_name]
(which can obviously be extended to any tuples)
to allow such access.
what do you experts think ?
Zero chance. plplgsql is a strongly typed language, and a
Bernd Helmle [EMAIL PROTECTED] writes:
--On Donnerstag, Februar 14, 2008 10:27:37 -0300 Alvaro Herrera
[EMAIL PROTECTED] wrote:
I wonder if it's possible to create a more compact output -- say, a
fixed-width column, with a letter for each enabled attribute, or a space
in the respective
Simon Riggs [EMAIL PROTECTED] writes:
LWLockAcquire(WALInsertLock, LW_EXCLUSIVE)
Reserve space to write into.
LSN = current Insert pointer
Move pointer forward by length of data to be inserted, acquiring
WALWriteLock if required to ensure space is available.
I think you've handwaved over
Alvaro Herrera a écrit :
[...]
For those that think that the \du output is currently OK because it
doesn't wrap, consider the french translation which is quite a bit wider
than the original:
alvherre=# \du
Liste des rôles
Nom du rôle | Superutilisateur |
Simon Riggs [EMAIL PROTECTED] writes:
Paul van den Bogaard (Sun) suggested to me that we could use more than
two WAL locks to improve concurrency.
After looking over the code I'm unconvinced that there's much win to be
bought this way. I had been thinking you could push a material amount
of
On Thu, 2008-02-14 at 13:52 -0500, Tom Lane wrote:
Simon Riggs [EMAIL PROTECTED] writes:
Paul van den Bogaard (Sun) suggested to me that we could use more than
two WAL locks to improve concurrency.
After looking over the code I'm unconvinced that there's much win to be
bought this way. I
Simon Riggs [EMAIL PROTECTED] writes:
On Thu, 2008-02-14 at 13:52 -0500, Tom Lane wrote:
[ still staring at the code ... ] Something that might be interesting
though is to try to move some of the buffer control logic overhead out
of WALInsertLock's domain and into WALWriteLock's domain.
I
Tom Lane escribió:
Now that psql prints multiline field values nicely, maybe it'd work
to fold all the boolean attributes into one column. I'm imagining
something like
Role name | Privileges | Member of
--+-+---
postgres | superuser | {}
|
On Fri, Feb 15, 2008 at 3:42 AM, Tom Lane [EMAIL PROTECTED] wrote:
Now that psql prints multiline field values nicely, maybe it'd work
to fold all the boolean attributes into one column. I'm imagining
something like
Role name | Privileges | Member of
Brendan Jurd [EMAIL PROTECTED] writes:
What about connection limit? I suppose we could combine it into the
privileges column, and refrain from displaying anything for no
limit.
5 connections seems a bit odd for a privilege. I'd be happy with
leaving that as a separate column. Or I guess we
On Fri, Feb 15, 2008 at 10:50 AM, Tom Lane [EMAIL PROTECTED] wrote:
Brendan Jurd [EMAIL PROTECTED] writes:
What about connection limit? I suppose we could combine it into the
privileges column, and refrain from displaying anything for no
limit.
5 connections seems a bit odd for a
On Feb 14, 2008, at 10:06 AM, Tom Lane wrote:
=?UTF-8?B?UmFwaGHDq2wgSmFjcXVvdA==?= [EMAIL PROTECTED] writes:
so, I propose the use of
NEW[variable_containing_the_column_name]
(which can obviously be extended to any tuples)
to allow such access.
what do you experts think ?
Zero
On Feb 14, 2008, at 7:27 AM, Alvaro Herrera wrote:
Attributes: S -- superuser
R -- create role
D -- create database
I -- inherit
Can we add something similar to the bottom of \z?
--
Decibel!, aka Jim C. Nasby, Database Architect [EMAIL PROTECTED]
Give your
On Feb 14, 2008, at 5:50 PM, Tom Lane wrote:
Brendan Jurd [EMAIL PROTECTED] writes:
What about connection limit? I suppose we could combine it into the
privileges column, and refrain from displaying anything for no
limit.
5 connections seems a bit odd for a privilege. I'd be happy with
On Fri, Feb 15, 2008 at 12:19 PM, Decibel! [EMAIL PROTECTED] wrote:
On Feb 14, 2008, at 7:27 AM, Alvaro Herrera wrote:
Attributes: S -- superuser
R -- create role
D -- create database
I -- inherit
Can we add something similar to the bottom of \z?
21 matches
Mail list logo
