Okay, after procrastinating for too long, I've just redone the Projects
Database so that it follows similar formats to the Application Database
that I built the other day...
I'm slowly going through the old database (600+ records) and migrating
them over to the new one, cleaning it out as I go a
--- Brandon Ibach <[EMAIL PROTECTED]> wrote:
> Quoting ^chewie <[EMAIL PROTECTED]>:
> > On Tue, 16 Nov 1999, Brandon Ibach wrote:
> >
> > BI>Can anybody explain what might be happening here?
> > BI>
> > BI> abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
> > BI> abc->pr
hi...
> Is it possible to log the transactions ( as complete statements ) on one
> database then process the logged transactions on the second database at
> intervals to keep it up to date?
>
transaction logging is already done on disk in pg_log, however you can't count
on it being correct (es
Quoting ^chewie <[EMAIL PROTECTED]>:
> On Tue, 16 Nov 1999, Brandon Ibach wrote:
>
> BI>Can anybody explain what might be happening here?
> BI>
> BI> abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
> BI> abc->procedure = vciceq, commutator = =* );
> BI> ERROR: parser:
On Tue, 16 Nov 1999, Brandon Ibach wrote:
BI>Can anybody explain what might be happening here?
BI>
BI> abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
BI> abc->procedure = vciceq, commutator = =* );
BI> ERROR: parser: parse error at or near "varchar"
BI>
BI>The fu
Ok, I've done this three times on 3 different machines, and get it wrong
each time...
I go through the INSTALL docs, compile, install, run initdb and then get:
"""...
File '/usr/local/pgsql/data/PG_VERSION' does not exist or no read
permission."""
It's not the latter, it's missing... it's not i
It seems that whenever we are doing a large operation -- eg, CREATE
INDEX on a sizable table, or VACUUM on a big database -- all other
postgres operations on that server stop dead. Attempts to do simple
operations on completely separate databases (but on the same server)
will hang (or perhaps th
Is it possible to log the transactions ( as complete statements ) on one
database then process the logged transactions on the second database at
intervals to keep it up to date?
RDW.
-Original Message-
From: Jeff Hoffmann <[EMAIL PROTECTED]>
To: Aaron J. Seigo <[EMAIL PROTECTED]>; [EMAIL
"Aaron J. Seigo" wrote:
> this needs to be in the back end... otherwise, if you have multiple people
> performing updates on different replicated servers, how can you guarentee
> concurancy? how do you manage the differences between read-only and updateable
> replicants? (this can be done using y
hi...
> my favorite hack is to wrap the c/c++ api so you can set up a group of
> mirror database connections and then calling the wrapped functions will
> call the original function on each of the mirror database connections.
> i've really never thought of it as something that should be part of
Can anybody explain what might be happening here?
abc=> create operator =* ( leftarg = varchar, rightarg = varchar,
abc->procedure = vciceq, commutator = =* );
ERROR: parser: parse error at or near "varchar"
The function "vciceq" already exists, and works. I've tried a
number of vari
11 matches
Mail list logo
