On Mon, Dec 13, 2004 at 15:17:49 -0200,
Alvaro Nunes Melo <[EMAIL PROTECTED]> wrote:
> db=> SELECT COUNT(*) FROM titulo WHERE cd_pessoa = 1;
> count
> ---
>220
> (1 record)
>
> Time: 48,762 ms
> db=> SELECT COUNT(*) FROM movimento WHERE cd_pessoa = 1;
> count
> ---
>221
> (1
Christoph Haller <[EMAIL PROTECTED]> writes:
> Furthermore, the regression test fails badly on
> parallel group (20 tests): point lseg
> running forever. The process list shows
> ps -fu rodos
> UID PID PPID CSTIME TTY TIME COMMAND
>rodos 14786 6955 228 10:26:43 pts/0
Hi,
I know that it's not very polite thing re-send a question, but I don't
have any idea about why can this be happening. I have two almost
identical tables, with equivalent indexes, but their performances are
very different. In this case, I'm sending the queries, explains,
tables'structures and r
[EMAIL PROTECTED] (Christoph Haller) writes:
> Has anybody accidentally hit this "postgressql.org"?
> I did.
>
> I don't know if freeloader is the correct english term for the
> german "Trittbrettfahrer", but that's what it looks like.
This is pretty common; people "speculatively" grab domain na
On Monday 13 December 2004 06:55 pm, Richard Huxton wrote:
> Kenneth Gonsalves wrote:
> > hi,
> > how does one replicate the myql 'set' datatype in pg? i tried using
> > 'check', but apparently there is much more to this
>
> You could use a bit-string if you are just tracking set membership, but
>
Kenneth Gonsalves wrote:
hi,
how does one replicate the myql 'set' datatype in pg? i tried using 'check',
but apparently there is much more to this
You could use a bit-string if you are just tracking set membership, but
that doesn't exactly duplicate the behaviour. It should be
straightforward e
On Dec 13, 2004, at 5:25 AM, Markus Schaber wrote:
Is there any way to hide schemas and relations a user does not have
access privileges for?
I suspect that the client (in this case, unavoidably excel via OLAP and
ODBC) gets this information via querying meta tables, so there is no
way
to protect
Markus Schaber wrote:
Hello,
Is there any way to hide schemas and relations a user does not have
access privileges for?
I suspect that the client (in this case, unavoidably excel via OLAP and
ODBC) gets this information via querying meta tables, so there is no way
to protect foreign schemas and rel
Has anybody accidentally hit this "postgressql.org"?
I did.
I don't know if freeloader is the correct english term
for the german "Trittbrettfahrer", but that's what it
looks like.
Regards, Christoph
---(end of broadcast)---
TIP 7: don't forge
I did 8.0.0rc1 - same behavior
psql template1
Welcome to psql 8.0.0rc1, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
hi,
how does one replicate the myql 'set' datatype in pg? i tried using 'check',
but apparently there is much more to this
regards
kg
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.or
Hello,
Is there any way to hide schemas and relations a user does not have
access privileges for?
I suspect that the client (in this case, unavoidably excel via OLAP and
ODBC) gets this information via querying meta tables, so there is no way
to protect foreign schemas and relations from beeing s
On Mon, 13 Dec 2004 09:27:04 +0530
Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> and while on this topic, how does one interpret the line numbers one
> gets when running psql -f to create tables?
Forget about line numbers. Add the -e option and your statements will
show up in your output. Here
13 matches
Mail list logo
