Thomas Lockhart <[EMAIL PROTECTED]> writes:
> Tom, can you refresh my memory on the preferred way to define
> "commutative operators" for operators with mixed input types? For
> example, I want to define a new operator to add an interval to a time.
> Do I need to fully implement the commutative fu
> As for replaying logs against a restored snapshot dump... AIUI, a
> dump records tuples by OID, but the WAL refers to TIDs. Therefore,
> the WAL won't work as a re-do log to recover your transactions
> because the TIDs of the restored tables are all different.
True for current way of bac
Tom, can you refresh my memory on the preferred way to define
"commutative operators" for operators with mixed input types? For
example, I want to define a new operator to add an interval to a time.
Do I need to fully implement the commutative function which adds a time
to an interval, or is there
On Thu, 30 Nov 2000, Nathan Myers wrote:
> After a power outage on an active database, you may have corruption
> at low levels of the system, and unless you have enormous redundancy
> (and actually use it to verify everything) the corruption may go
> undetected and result in (subtly) wrong answe
On Thu, 30 Nov 2000, Nathan Myers wrote:
> On Thu, Nov 30, 2000 at 07:02:01PM -0400, The Hermit Hacker wrote:
> >
> > v7.1 should improve crash recovery ...
> > ... with the WAL stuff that Vadim is producing, you'll be able to
> > recover up until the point that the power cable was pulled out of
On Thu, Nov 23, 2000 at 07:58:29AM -0800, some SMTP stream spewed forth:
> At 09:44 AM 11/21/00 -0700, Tim Uckun wrote:
>
> >What about the php module? Does it take advantage of API?
>
> I don't know. If not, though, there wouldn't be much point in using
> AOLserver, since the simple and effic
Hi:
I posted this in pgsql-general last week, but I got no answer. Maybe I
have better luck this time?
TIA.
--
Alvaro Herrera ()
-- Forwarded message --
Date: Tue, 21 Nov 2000 17:26:54 -0300 (CLST)
From: Alvaro Herrera <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [GENERA
On Thu, Nov 30, 2000 at 07:02:01PM -0400, The Hermit Hacker wrote:
>
> v7.1 should improve crash recovery ...
> ... with the WAL stuff that Vadim is producing, you'll be able to
> recover up until the point that the power cable was pulled out of
> the wall.
Please do not propagate falsehoods li
At 07:50 PM 11/30/00 -0600, GH wrote:
>On Thu, Nov 23, 2000 at 07:58:29AM -0800, some SMTP stream spewed forth:
>> At 09:44 AM 11/21/00 -0700, Tim Uckun wrote:
>>
>> >What about the php module? Does it take advantage of API?
>>
>> I don't know. If not, though, there wouldn't be much point in u
At 05:15 PM 11/30/00 -0800, Nathan Myers wrote:
>As for replaying logs against a restored snapshot dump... AIUI, a
>dump records tuples by OID, but the WAL refers to TIDs. Therefore,
>the WAL won't work as a re-do log to recover your transactions
>because the TIDs of the restored tables are a
On Thu, Nov 30, 2000 at 05:37:58PM -0800, Mitch Vincent wrote:
> > > No, WAL does help, cause you can then pull in your last dump and recover
> > > up to the moment that power cable was pulled out of the wall ...
> >
> > False, on so many counts I can't list them all.
>
> Why? If we're not talkin
On Thu, 30 Nov 2000, Nathan Myers wrote:
> On Thu, Nov 30, 2000 at 07:47:08PM -0400, The Hermit Hacker wrote:
> > On Thu, 30 Nov 2000, Don Baccus wrote:
> > > At 07:02 PM 11/30/00 -0400, The Hermit Hacker wrote:
> > > >
> > > >v7.1 should improve crash recovery for situations like this ... you'll
On Thu, 30 Nov 2000, Nathan Myers wrote:
> On Thu, Nov 30, 2000 at 07:47:08PM -0400, The Hermit Hacker wrote:
> > On Thu, 30 Nov 2000, Don Baccus wrote:
> > > At 07:02 PM 11/30/00 -0400, The Hermit Hacker wrote:
> > > >
> > > >v7.1 should improve crash recovery for situations like this ... you'll
> > No, WAL does help, cause you can then pull in your last dump and recover
> > up to the moment that power cable was pulled out of the wall ...
>
> False, on so many counts I can't list them all.
Why? If we're not talking hardware damage and you have a dump made sometime
previous to the crash,
On Thu, Nov 30, 2000 at 07:47:08PM -0400, The Hermit Hacker wrote:
> On Thu, 30 Nov 2000, Don Baccus wrote:
> > At 07:02 PM 11/30/00 -0400, The Hermit Hacker wrote:
> > >
> > >v7.1 should improve crash recovery for situations like this ... you'll
> > >still have to do a recovery of the data on cor
eject
--MIME Multi-part separator--
On Thu, 30 Nov 2000, Michael Fork wrote:
> I was wondering if someone could tell me if I have gotten the fields of
> tgargs correct:
For foreign key constraints, yes. Other triggers can use tgargs for
whatever they want.
> \000 -- Constraint name?
Yes.
> foreign_table_multi\000 -- table with
On Thu, 30 Nov 2000, Don Baccus wrote:
> At 07:02 PM 11/30/00 -0400, The Hermit Hacker wrote:
> >
> >v7.1 should improve crash recovery for situations like this ... you'll
> >still have to do a recovery of the data on corruption of this magnitude,
> >but at least with the WAL stuff that Vadim is
At 07:02 PM 11/30/00 -0400, The Hermit Hacker wrote:
>
>v7.1 should improve crash recovery for situations like this ... you'll
>still have to do a recovery of the data on corruption of this magnitude,
>but at least with the WAL stuff that Vadim is producing, you'll be able to
>recover up until the
v7.1 should improve crash recovery for situations like this ... you'll
still have to do a recovery of the data on corruption of this magnitude,
but at least with the WAL stuff that Vadim is producing, you'll be able to
recover up until the point that the power cable was pulled out of the wall
...
I was wondering if someone could tell me if I have gotten the fields of
tgargs correct:
\000 -- Constraint name?
foreign_table_multi\000 -- table with foreign key(s)
primary_table_multi\000 -- table with primary key(s)
UNSPECIFIED\000 -- ??
foreign_int_1\000 -- 1st field in fore
At 10:52 AM 11/30/00 -0500, Tom Lane wrote:
>Don Baccus <[EMAIL PROTECTED]> writes:
>> The optimizer should do a better job on your first query, sure, but why
>> don't you like writing joins?
>
>The join wouldn't give quite the same answers. If there are multiple
>rows in table2 matching a partic
If you installed in the default directory then the files relating to a
database are in
/usr/local/pgsql/data/base/
So you could just total up the size of everything under that directory.
-Mitch
- Original Message -
From: "Guus Kerpel" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Mo
Tom Lane writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > I don't like the code in fe-connect.c one bit, it's way messed up.
>
> Yes. We've accepted several extremely questionable (not to mention
> poorly documented or completely undocumented) "features" in there
> recently. If I'd be
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> I'm going to disable the URL patch, since it doesn't seem to work and
> breaks legitimate uses of database names with funny characters. The
> service patch seemed kind of useful, but since it's not documented and I
> don't feel like finding out, I th
Hi everybody,
there must be a nice way of getting the size of my database (in mB,
preferably), but I couldn't find it in the documentation that I searched
through briefly.
The reason why I wanna do this is because the server might get full quickly
and to make sure it doensn't happen before I kn
* Arno A. Karner <[EMAIL PROTECTED]> [001130 10:09]:
> thanks for the infor commented out define complex macro poof compiles :)
> initdb works :)
> createuser, createdb fail :( no entry in pg_hba.conf, have looked at it
> looks like the standard default one on my linux box has entries for
> local
thanks for the infor commented out define complex macro poof compiles :)
initdb works :)
createuser, createdb fail :( no entry in pg_hba.conf, have looked at it
looks like the standard default one on my linux box has entries for
local and for host 127.0.0.1
i would search the archives but when i t
Don Baccus <[EMAIL PROTECTED]> writes:
> The optimizer should do a better job on your first query, sure, but why
> don't you like writing joins?
The join wouldn't give quite the same answers. If there are multiple
rows in table2 matching a particular table1 row, then a join would give
multiple c
At 05:24 AM 11/30/00 +, Thomas Lockhart wrote:
>> Is "if" clause support in PG?
>> for example:
>> "drop table aa if exist"
>> "insert into aa values(1) if not exists select * from aa where i=1"
>
>No. afaict it is not in any SQL standard, so is unlikely to get much
>attention from developers.
At 08:37 AM 11/30/00 -0500, mlw wrote:
>> mlw wrote:
>> >
>> > Why is a "select * from table1 where field in (select field from table2
>> > where condition )"
>> >
>> > is so dramatically bad compared to:
>> >
>> > "select * from table1, table2 where table1.field = table2.field and
>> > condition"
"Arno A. Karner" <[EMAIL PROTECTED]> writes:
> epcg compiles but fails with unresolved var
> nocachegetattr in pgc.o
This is a header bug (there's a backend header file that some bright
soul put a static function declaration into :-( ... and the function
can't link outside the backend ... and ecp
mlw wrote:
>
> Hannu Krosing wrote:
> >
> > mlw wrote:
> > >
> > > Why is a "select * from table1 where field in (select field from table2
> > > where condition )"
> > >
> > > is so dramatically bad compared to:
> > >
> > > "select * from table1, table2 where table1.field = table2.field and
> > >
try this
SELECT age(max(h_date), now()) FROM table WHERE email='hawks@vsnl';
Michael Fork - CCNA - MCP - A+
Network Support - Toledo Internet Access - Toledo Ohio
On Thu, 30 Nov 2000, Manish Vig wrote:
> Dear Sir,
> thanks for the reply.
> I tried select now()
> but it give
Hannu Krosing wrote:
>
> mlw wrote:
> >
> > Why is a "select * from table1 where field in (select field from table2
> > where condition )"
> >
> > is so dramatically bad compared to:
> >
> > "select * from table1, table2 where table1.field = table2.field and
> > condition"
> >
> > I can't underst
mlw wrote:
>
> Why is a "select * from table1 where field in (select field from table2
> where condition )"
>
> is so dramatically bad compared to:
>
> "select * from table1, table2 where table1.field = table2.field and
> condition"
>
> I can't understand why the first query isn't optimized be
ive got the backend stuff to compile on sco with the sdk had to add
-lsocket
to get rid of unresolved var gethostbyaddress. made it as far as
compiling
epcg compiles but fails with unresolved var
nocachegetattr in pgc.o
is this a yacc/lex issue if so what would be min version requirements
for
b
When Postgres is fast, it is really fast. I love it. My biggest problem
is when/how it chooses best path, it seems to me that relatively few
records with a high duplication destroy performance. I can't stress
enough that this is a serious problem in the real world.
Take these two queries:
cdinfo
38 matches
Mail list logo