On Dec 31, 2003, at 14:16, Chris Ochs wrote:
Now what our application does is create the queries as it runs, then
instead
of inserting them into the database it writes them all out to a single
file
at the end of the transaction. This is a huge performance boost. We
then
use a separate deamon
On Thu, 1 Jan 2004, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > 186_archives=# \d ndict7
> > Table "public.ndict7"
> > Column | Type | Modifiers
> > -+-+
> > url_id | integer | not null default 0
> > word_id | integer | not null defau
Marc G. Fournier wrote:
> 186_archives=# \d ndict7
> Table "public.ndict7"
> Column | Type | Modifiers
> -+-+
> url_id | integer | not null default 0
> word_id | integer | not null default 0
> intag | integer | not null default 0
> Indexes
On Wed, 31 Dec 2003, Dave Cramer wrote:
> What is the locale of the database?
>
> like won't use an index, unless it is 'C' locale, or you use 7.4 and
> change the operator of the index.
one thing I failed to note ... this is all running on 7.4 ... under 7.3,
it was much much worse :)
Marc
What is the locale of the database?
like won't use an index, unless it is 'C' locale, or you use 7.4 and
change the operator of the index.
Dave
On Wed, 2003-12-31 at 20:49, Marc G. Fournier wrote:
> On Wed, 31 Dec 2003, Bruce Momjian wrote:
>
> > Marc G. Fournier wrote:
> > > On Wed, 31 Dec 2003
On Wed, 31 Dec 2003, Dave Cramer wrote:
> In fact this is a very bad advertisement for postgres
I just posted a very very long email of what I'm seeing in the logs, as
well as various query runs ... it may just be something that I need to
tune that I'm overlooking:( the queries aren't particular
On Wed, 31 Dec 2003, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Wed, 31 Dec 2003, Bruce Momjian wrote:
> >
> > > > Out of everything I've found so far, mnogosearch is one of the best ... I
> > > > just wish I could figure out where the bottleneck for it was, since, from
> > > > reading
On Wed, 2003-12-31 at 18:43, Bruce Momjian wrote:
> Marc G. Fournier wrote:
> > On Tue, 30 Dec 2003, Joshua D. Drake wrote:
> >
> > > Hello,
> > >
> > > Why are we not using Tsearch2?
> >
> > Because nobody has built it yet? Oleg's stuff is nice, but we want
> > something that we can build into
On Wed, 31 Dec 2003, Mike Nolan wrote:
> That raises an interesting question. Can pg be configured so
> that user tables MUST be in user schemas, i.e., nobody can put tables
> in the PUBLIC schema?
Sure, you can simply drop the public schema, or "revoke all on schema
public from public";
Kris
This concept of using complex types in tables actually does have one
legitimate use. When used with casts and functions, you could use it as a
"poor-man's datatype" development method.
Here is a hypothetical example. Imagine for a moment that there was no CIDR
datatype. I could create a dataty
4908*2=9816
2 inserts on the same line in the dmp file?
Erwan
>>> Együd Csaba <[EMAIL PROTECTED]> 31/12/2003 09:58:25 >>>
Hi all,
I tried to dump out a single table and just for a verification I counted the
number of 'INERT INTO' rows.
I found that count(*) results less rows than grep.
**
Marc,
At our website we had a "in database" search as well... It was terribly
slow (it was a custom built vector space model implemented in mysql+php
so that explains a bit).
We replaced it by the Xapian library (www.xapian.org) with its Omega
frontend as a middle end. I.e. we call with our ph
On Wed, 31 Dec 2003, Tony wrote:
>
> I have been a consultant with Microsoft Operating Systems for sometime
> now, but never sat any of their exams, because my experience with
> Network Operating Systems speaks for itself. I've never had my
> abilities questioned by an employer (only by emplo
This is exactly why I got my Cisco CCNA qualification, not because I
wanted to work with Cisco Routing equipment (because quite frankly I
can't think of a duller subject) but because I could show potential
employers/clients a well rounded skill set. This means I can appreciate
implications bro
Hi all,
I tried to dump out a single table and just for a verification I counted the
number of 'INERT INTO' rows.
I found that count(*) results less rows than grep.
***
[EMAIL PROTECTED] ~
$ pg_dump -d -t t_stockchanges alumil6 > sc.dump
***
alumil6=# select count
15 matches
Mail list logo
