On Thursday 05 December 2002 23:21, Peter Eisentraut wrote:
> Tom Lane writes:
> > I was going to add one for schemas, but \ds and \dS are already taken,
> > and there was no good proposal for what to use instead. Any thoughts?
>
> \dschema
>
> Pretty soon we'll have too many things for 'c' as wel
But why shadow happens only schema name is SAME as username??
Jie
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 05, 2002 2:58 PM
To: Jie Liang
Cc: 'Bruce Momjian'; [EMAIL PROTECTED]
Subject: Re: why schema name is same as username behaves different
Jie Liang wrote:
I expect to see something like:
List of relations
Schema | Name | Type | Owner
+--+---+---
public | foo | table | robot
t | foo | table | robot
That's because schema t is not in your search path. By default,
search path is:
regression=#
Got it.
Thank you.
Jie
-Original Message-
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 05, 2002 2:58 PM
To: Jie Liang
Cc: 'Bruce Momjian'; [EMAIL PROTECTED]
Subject: Re: why schema name is same as username behaves different then
others
Jie Liang <[EMAIL PROTECTED
Tom Lane writes:
> I was going to add one for schemas, but \ds and \dS are already taken,
> and there was no good proposal for what to use instead. Any thoughts?
\dschema
Pretty soon we'll have too many things for 'c' as well, so maybe we should
go with full words.
--
Peter Eisentraut [EMAI
Jie Liang <[EMAIL PROTECTED]> writes:
> I expect to see something like:
You're neglecting the effects of search path. \dt only shows what's
visible in your search path. (IIRC, \dt *.* is the easiest way to
see all tables regardless of search path.)
> it seems if schema name is same as
Note:
test=# super user postgres
test=> regular user robot
### comments
test=#create schema t AUTHORIZATION robot;
CREATE SCHEMA
test=> select * from pg_namespace ;
nspname | nspowner | nspacl
+--+
pg_catalog |1 | {=U}
pg_toast |1 | {=}
public
I believe \dn is better.
Jie Liang
Software Engineer
St. Bernard Software
16882 W. Bernardo Dr.
San Diego, CA 92127
Tel: 858-524-2134
Fax:858-676-2228
[EMAIL PROTECTED]
-Original Message-
From: Bruce Momjian [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 05, 2002 12:36 PM
T
How about \D for Domains...
BTW, because many people ask how to do the equivalant in SQL of a \
command,
why not be done with the \ commands which are criptic anyway and instead
create global stored procedures like:
sp_list_databases()
sp_list_schemas()
sp_list_{whatever}()
sp_enable_{this}()
sp_
We just upgraded our development server (Redhat 7.1) to PostgreSQL 7.3
(last night) and have been using phpPgAdmin for various functions. It
seems that phpPgAdmin-2.4.2 (Released in July) doesn't work completely
with PostgreSQL 7.3. Our big problem is that trying to do an SQL dump
of a database g
--On Thursday, December 05, 2002 15:33:01 -0500 Tom Lane
<[EMAIL PROTECTED]> wrote:
Bruce Momjian <[EMAIL PROTECTED]> writes:
Also, on TODO I see:
* Add schema, cast, and conversion backslash commands to psql
so we know we need them.
I was going to add one for schemas, but \ds and \dS are a
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Also, on TODO I see:
> > * Add schema, cast, and conversion backslash commands to psql
> > so we know we need them.
>
> I was going to add one for schemas, but \ds and \dS are already taken,
> and there was no good proposal for wh
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Also, on TODO I see:
> * Add schema, cast, and conversion backslash commands to psql
> so we know we need them.
I was going to add one for schemas, but \ds and \dS are already taken,
and there was no good proposal for what to use instead. Any thou
Due to a late-night typo, the 7.3-1 RPMset released last night would start the
postmaster for the first time, but not subsequent times. I have corrected
the problem and uploaded a 7.3-2 RPMset. If you do not want to download the
whole set again to fix a single-character bug, edit the file
/et
On Thursday 05 December 2002 14:23, Radoslaw Stachowiak wrote:
> postgresql.init script contains line:
>
> if [ `cat $PGDATA/PG_VERSION` != '7.2' ]
>
> while it of course should be:
>
> if [ `cat $PGDATA/PG_VERSION` != '7.3' ]
Argh. It'll start ONCE, but not TWICE.
Also, on TODO I see:
* Add schema, cast, and conversion backslash commands to psql
so we know we need them.
---
Jie Liang wrote:
> Bruce,
>
> I wonder which command can show all schemas in 7.3?
> I mean:
> \dt --
We should have one, but the only solution now is:
test=> select * from pg_namespace;
---
Jie Liang wrote:
> Bruce,
>
> I wonder which command can show all schemas in 7.3?
> I mean:
> \dt -- show all tables
> \l --
postgresql.init script contains line:
if [ `cat $PGDATA/PG_VERSION` != '7.2' ]
while it of course should be:
if [ `cat $PGDATA/PG_VERSION` != '7.3' ]
.radek.
---(end of broadcast)---
TIP 3: if posting/read
Andreas Schmitz wrote:
> On Wednesday 04 December 2002 17:47, Tom Lane wrote:
> > Andreas Schmitz <[EMAIL PROTECTED]> writes:
> > > ist there any way to cancel a user query as dba ?
> >
> > Send a SIGINT to the backend process running that query, eg
> >
> > kill -INT
> >
> > This has the same
I don't think you can drop/recreate the sequence because the dependency
code knows other tables depend on it.
---
Rajesh Kumar Mallah. wrote:
>
> Doesn't dropping and recreating the sequence suit the bill ?
>
> whats' the
Bruce,
I wonder which command can show all schemas in 7.3?
I mean:
\dt -- show all tables
\l -- show all databases
?? -- show all schemas
Thanks.
Jie Liang
Software Engineer
St. Bernard Software
16882 W. Bernardo Dr.
San Diego, CA 92127
Tel: 858-524-2134
Fax:858-676-2228
[EMAIL PROTECTE
Guys, I've have a legacy summary table ( monitor_summary ) which represents
a count of the number of records in another table ( document_status ).
Here are the table definitions.
CREATE TABLE monitor_summary (
id SERIAL PRIMARY KEY, -- Internal ID
If you wanted to do something programatically, couldn't you define some
functions that would allow you say implement a query id, and embed a
function call in the where clause like
select getNextQueryId()
where .. and queryStillActive(query_id) = true
Then another function could be called to
I was testing this on a 7.3 beta the other week to try to make it work
with LDAP authentication, and I think I only got it working if I bypased
the system-auth PAM file that everything was normally funneled through.
I don't know exactly why it wasn't working, but whenever I put a line
that use
On Wednesday 04 December 2002 17:47, Tom Lane wrote:
> Andreas Schmitz <[EMAIL PROTECTED]> writes:
> > ist there any way to cancel a user query as dba ?
>
> Send a SIGINT to the backend process running that query, eg
>
> kill -INT
>
> This has the same effect as a user-requested cancel (eg ^
Doesn't dropping and recreating the sequence suit the bill ?
whats' the major advantage to implement em as a command?
At least one thing from which all of us can benifit in PgSQL
is replication. I just hope 7.4 give us some sort of master/slave replication.
Regds
Mallah.
On Wednesday 04 Dece
by total no of triggers that relation has,
which is got from a subselct on pg_triggers
On Thursday 05 December 2002 10:24 am, shreedhar wrote:
> Hi Bhuvan & Mallah,
>
> Have you checked desabling of triggers. What reltriggers represent. If we
> set it as '0' to enable by what value it has to be u
27 matches
Mail list logo
