Doug McNaught wrote:
"Magnus Naeslund(t)" <[EMAIL PROTECTED]> writes:
I have this big table running on an old linux install (kernel 2.2.25).
I've COPYed some tcpip logs into a table created as such:
Linux is probably killing your process because it (the kernel) is low
on memory. Unfortunately,
On Thu, 4 Dec 2003, E.Rodichev wrote:
> On Wed, 3 Dec 2003, Stephan Szabo wrote:
>
> > Only the locale settings at initdb time matter. Changing the LC_* later
> > is not going to change what the database does. Encoding and locale are
> > separate (but related) and it is your responsibility to ma
"Magnus Naeslund(t)" <[EMAIL PROTECTED]> writes:
> I have this big table running on an old linux install (kernel 2.2.25).
> I've COPYed some tcpip logs into a table created as such:
Linux is probably killing your process because it (the kernel) is low
on memory. Unfortunately, this happens more
Hackers
Here is the definition of relation_byte_size() in optimizer/path/costsize.c:
--
/*
* relation_byte_size
*Estimate the storage space in bytes for a given number of tuples
*of a given width (size in byte
Andrew Dunstan <[EMAIL PROTECTED]> wrote:
> Tom Lane wrote:
>
>>[EMAIL PROTECTED] (David Fetter) writes:
>>
>>
>>>While PL/Perl is great, it's not available everywhere, and I'd like
>>>to be able to grab atoms from a regex match in, say, a SELECT. Is
>>>there some way to get access to them?
>>
I have this big table running on an old linux install (kernel 2.2.25).
I've COPYed some tcpip logs into a table created as such:
create table ipstats (time timestamp, src inet, dst inet, npackets int8,
nbytes int8);
Big:
select count(*) from ipstats;
count
--
99173733
When i do two s
On Wed, 3 Dec 2003, Stephan Szabo wrote:
> Only the locale settings at initdb time matter. Changing the LC_* later
> is not going to change what the database does. Encoding and locale are
> separate (but related) and it is your responsibility to make sure the
> choices are consistent. If you do
On Wed, 3 Dec 2003, Andrew Dunstan wrote:
> Encoding and collation order are two different things. LC_* settings
> have no effect on encoding.
>
> see http://www.postgresql.org/docs/current/static/charset.html
I am trying to point out to reverse dependency:
encoding (1) has effect on LC_* settin
On Wed, 3 Dec 2003, Alvaro Herrera wrote:
> On Wed, Dec 03, 2003 at 11:42:34PM +0300, E.Rodichev wrote:
> > On Wed, 3 Dec 2003, Stephan Szabo wrote:
> >
> > > No, it isn't. As far as PostgreSQL is concerned the database is SQL_ASCII
> > > since you didn't override the default encoding at initdb ti
On Wed, 3 Dec 2003, E.Rodichev wrote:
> On Wed, 3 Dec 2003, Stephan Szabo wrote:
>
> >
> > On Wed, 3 Dec 2003, E.Rodichev wrote:
> >
> > > On Fri, 28 Nov 2003, Tom Lane wrote:
> > >
> > > > "E.Rodichev" <[EMAIL PROTECTED]> writes:
> > > > > /e:2>createdb test
> > > >
> > > > > test | er
On Wed, Dec 03, 2003 at 11:42:34PM +0300, E.Rodichev wrote:
> On Wed, 3 Dec 2003, Stephan Szabo wrote:
>
> > No, it isn't. As far as PostgreSQL is concerned the database is SQL_ASCII
> > since you didn't override the default encoding at initdb time or at
> > createdb time. You did choose LC_ valu
E.Rodichev wrote:
On Wed, 3 Dec 2003, Stephan Szabo wrote:
On Wed, 3 Dec 2003, E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
"E.Rodichev" <[EMAIL PROTECTED]> writes:
/e:2>createdb test
test | er | SQL_ASCII <- Incorrect!
(3 rows)
On Wed, 3 Dec 2003, Stephan Szabo wrote:
>
> On Wed, 3 Dec 2003, E.Rodichev wrote:
>
> > On Fri, 28 Nov 2003, Tom Lane wrote:
> >
> > > "E.Rodichev" <[EMAIL PROTECTED]> writes:
> > > > /e:2>createdb test
> > >
> > > > test | er | SQL_ASCII <- Incorrect!
> > > > (3 rows)
> > >
> >
julius <[EMAIL PROTECTED]> writes:
> tuptoaster.c: In function `toast_delete_datum':
> tuptoaster.c:973: `F_OIDEQ' undeclared (first use in this function)
This suggests that the src/backend/utils/Gen_fmgrtab.sh script did not
execute correctly. With no details about your platform, it's hard to
sa
im not sure if this is the correct mailing list, please correct me if it is not.
my gcc is version 3.2, configure runs fine i deativated readline-support...but this
error occours:
gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes -Wmissing-declarations
-I../../../../src/include -D_GNU_SOUR
Hello:
I am trying to find out, how is the B-tree index implemented for
multiple columns? does Postgres, just
concatenate the columns --- if this is the case, then how is the
search performed? Also, does the optimizer
choose the index, only when the constraining is
On Wed, 3 Dec 2003, E.Rodichev wrote:
> On Fri, 28 Nov 2003, Tom Lane wrote:
>
> > "E.Rodichev" <[EMAIL PROTECTED]> writes:
> > > /e:2>createdb test
> >
> > > test | er | SQL_ASCII <- Incorrect!
> > > (3 rows)
> >
> > > Let's note than the last line is in fact completely incorre
Tom Lane wrote:
[EMAIL PROTECTED] (David Fetter) writes:
While PL/Perl is great, it's not available everywhere, and I'd like to
be able to grab atoms from a regex match in, say, a SELECT. Is there
some way to get access to them?
There's a three-parameter variant of substring() that allows
E.Rodichev wrote:
On Fri, 28 Nov 2003, Tom Lane wrote:
"E.Rodichev" <[EMAIL PROTECTED]> writes:
/e:2>createdb test
test | er | SQL_ASCII <- Incorrect!
(3 rows)
Let's note than the last line is in fact completely incorrect.
What's incorrect about it?
On Tue, 2003-12-02 at 23:12, Marc G. Fournier wrote:
>
> Please take a quick peak at it ...
>
> ftp://ftp.postgresql.org/pub/source/v7.3.5
>
>
>
> Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
> Email: [EMAIL PROTECTED] Yahoo!: yscrappy
E.Rodichev writes:
> It is incorrect, because database "test" is, really, in KOI8, NOT in SQL_ASCII
> in this example, as I explained in my mail.
The encoding is only a declaration of your intentions. What you actually
put into the database is your responsibility.
--
Peter Eisentraut [EMAIL
On Fri, 28 Nov 2003, Tom Lane wrote:
> "E.Rodichev" <[EMAIL PROTECTED]> writes:
> > /e:2>createdb test
>
> > test | er | SQL_ASCII <- Incorrect!
> > (3 rows)
>
> > Let's note than the last line is in fact completely incorrect.
>
> What's incorrect about it? You didn't ask for an
Fairly good idea IMHO, especially considering Christopher's point
about the unlikeliness of needing an exact count anyway.
Regards, Christoph
>
> How about:
>
> Implement a function "estimated_count" that can be used instead of
> "count". It could use something like the algorithm in
> src/
How about:
Implement a function "estimated_count" that can be used instead of
"count". It could use something like the algorithm in
src/backend/commands/analyze.c to get a reasonably accurate psuedo count
quickly.
The advantage of this approach is that "count" still means (exact)count
(for yo
24 matches
Mail list logo
