Satyajeet Seth wrote:
>
> Hi
> The query:
> select * from webdata except select * from webdata1;
> takes abysmally long .How can I optimise it?
> The particulars are:
You could try
select * from webdata w
where not exists
(select * from webdata1 w1
where w1.tid=w.tid
Hi Manuel,
If security is an issue then it is a good idea to keep the part of the
application that accesses the database on a secure system. Because a lot of
bad things are possible if the entire application runs on an uncontrolled
client and is given great authority and direct access to the data
Hi,
I seem to have a problem here. When I try to insert a tuple that is
larger than 8192 bytes, I get an error message saying that the tuple is
too large. Ok, that's fine. But the problem is that the table seems to
become corrupted. After I do this insert statement I went to psql and
did a se
> no, you won't ;-)
> further testing indicates that current_stamp like current, instead of
> now/now().
Now I am confused. You say there is a difference between them?
--
Bruce Momjian| http://www.op.net/~candle
[EMAIL PROTECTED]| (610) 853-3000
+
no, you won't ;-)
further testing indicates that current_stamp like current, instead of
now/now().
also, I remembered (I tried to check the archive, but failed) now() should
not be use in where clause, cos it will hurt performance.
Kai
On Wed, 1 Dec 1999, Bruce Momjian wrote:
> > Ed Loehr ha
Hi,
How can I change the definition of a function without breaking all
tables, which use the function?
Sascha
On Wed, 1 Dec 1999 [EMAIL PROTECTED] wrote:
> yes. good for netscape. I forgot I hate M$ ;-)
> I'm going to read it word by word to systemize my sql/pg knowledge.
>
> Another thing: the general and sql mailing lists' search do not work now.
> they only return 1,2,3,... empty links, no content.
hi,
Does anyone know of a thechnical brief on Pg I can look up and read? For example how
it spawns a new process, uses mem, and what not. Not detailed algorithms, but an
overview of how it works; and maybe a why.
If no such animal exists, perhaps, is a few people are interested, we coudl put
> Ed Loehr ha scritto:
>
> > Just curious: anyone have any comment on any practical differences between now()
>and CURRENT_TIMESTAMP, which seems to work
> > the same?
> >
>
> I think it is the same function, both of them return the current date and time.
>
> now() should be the internal post
yes. good for netscape. I forgot I hate M$ ;-)
I'm going to read it word by word to systemize my sql/pg knowledge.
Another thing: the general and sql mailing lists' search do not work now.
they only return 1,2,3,... empty links, no content.
thanks!
On Wed, 1 Dec 1999, Bruce Momjian wrote:
> >
Hi
The query:
select * from webdata except select * from webdata1;
takes abysmally long .How can I optimise it?
The particulars are:
tracedb=> \d webdata
Table= webdata
+--+--+---+
| Field |
Ed Loehr ha scritto:
> Just curious: anyone have any comment on any practical differences between now()
>and CURRENT_TIMESTAMP, which seems to work
> the same?
>
I think it is the same function, both of them return the current date and time.
now() should be the internal postgreSQL function.
a
Answering part of my own questions, it appears the latest thinking on this problem (in
http://www.deja.com/getdoc.xp?AN=542994084) is that it stems from indexed columns
greater
than half a page (~4K), and/or a previous insert having been interrupted by
elog(ERROR) or
a backend crash. The latter
Bruce Momjian wrote:
> > Peter Eisentraut wrote:
> >
> > > This is getting to be our favourite error message...
> > >
> > > It is caused by a corrupted B-Tree index. Drop and recreate that one.
> >
> > Thanks. Unfortunately, the lack of context to the error message makes it difficult
> > to iden
> isfiji=> explain select * from sessions;
> NOTICE: QUERY PLAN:
> Seq Scan on sessions (cost=21330.73 size=371719 width=138)
> EXPLAIN
>
> The query above can access over 250M of memory according to top but dies
> with either a seg fault or the latest, something called
> "calloc: Cannot alloc
Hello,
I've looked over the list archives before, and didn't see anything about
this thencan't check now as I'm having problems getting on to the web
server :(
I'm using the pg_passwd script to create password files that are
referenced via the pg_hba.conf file. Each user has a different file
now is a constant, while now() is a function. so, to me,
it should be always now unless you really need now().
what's more, in my impression, now() is not in any official
doc, it is like a rescue for now. however, in this case,
seems there is not much difference.-- oops
as for current_timesta
Hi all,
I guess that the postgres it-self is not designated as a multi-threaded
server. I was wondering if the library is instead thread safe (i.e.: if
it can be safely called from multi-threaded applications).
Thanks in advance
Massimo
I can not get THE book's pdf link. Not sure whether it
is my side's irregular firewall issue. If in that case,
can it be a http link? I guess I question/request is:
seems the ftp link is broken? if not, can it be a http one?
thanks
Kai
Sir:
I working on an application that needs to access the postgresql
database using a web page. Java was suggested to me as a very good
platform. Can anyone give me some ideas where i can obtain some components
like the database components available to delphi or visual basic which i
can use in
20 matches
Mail list logo
