Hello,
I don't really know since when those commands are provided by psql, but I
found them recently and was quite annoyed by the output given by both of
them.
Though I find that the \du command's output is quite accurate, I wonder why
\dg gives the same informations ?
I would have expected to s
Le mercredi 19 mars 2008, Albert Cervera i Areny a écrit :
Hi !
> A Dimecres 19 Març 2008, Nikolay Samokhvalov va escriure:
> > 2. Why the query above provides 4 rows, not 2*4=8? Actually, that's
> > interesting -- I can use this query to find l.c.m. But it's defenetely
> > not that I'd expect be
Hello,
I've seen that postgreSQL tries to follow sql standards as far as possible,
and that sometimes (often) brings it's own extentions. I've thought of one
concerning the sql command create table like.
As far as I've understood the documentation, one can create a table using
another table as a
Le mardi 26 février 2008, Tom Lane a écrit :
>
> In short, what I think we need here is just some more conveniently
> defined extraction filter switches than --schema-only and --data-only.
> There's no need for any fundamental change to pg_dump's architecture.
Forgive me if what I will say bellow
Le lundi 25 février 2008, Leonardo Cezar a écrit :
Hi Leonardo,
Thanks for your quick answer, I didn't know it was a TODO item, and that
somepeople were working on it... Keep going, then, cause I'm really waiting
for these features !
> On Mon, Feb 25, 2008 at 10:48 AM, D
Hi all,
On the 6th of february, there's been a thread about adding new options to
pg_dump, but it is now too late for me to add comments to this thread, since
all that was said wouldn't be readable at this time, so I add an new thread
here.
I haven't found any option to dump any user-defined fun
Le vendredi 9 novembre 2007, vous avez écrit :
> David BOURIAUD wrote:
> > if the run-time option is chosen, any message issued by any command, from
> > connexion to all sql commands launched in any way by a user should go in
> > a separate log file, that could be named log
Hi to all,
Could it be possible to have informations about who do what on any tablespace
or database logged in separate files, as samba does.
I don't think that it should be the default way, since the way events are
logged by now seems to please all users, but I'd think that a run-time option
c
