Christopher Browne wrote:
> > To ensure high availability, using DRBD to replicate the storage or
> > using a shared storage (e.g., EMC^2) does the job. That saves you
> > the trouble of having to set up and manage a database replication
> > solution at all.
>
> Regrettably, "disk replication" sch
I have just upgraded my development machine from 7.3.4 to 7.4.2 and have a
couple of small questions which I can't find any answers to in the documents or
history.
1) What does the TRIGGER group/user privilege mean when applied to a VIEW?
(after the upgrade all groups that had access rights to vie
Hello Brad,
We've now done a couple of projects where it was essential to have full,
real time replication (for traceability & legal reasons).
The way we approached it was to do the replication ourselves at the
application level. This isn't as hard as it sounds: you just open 2 db
connections (1
- Original Message -
> On Tuesday 13 April 2004 16:43, Donald Fraser wrote:
> > I am trying to build Postgres 7.4.2 from the source rpm on Red Hat Linux
> > 7.1 2.96-98
>
> While I do test builds on a Red Hat 7.3 compatible system, I do not do so on
a
> 7.1 system. Sorry.
>
> > I get the
Thanks to those who offered help,
The suggested solutions are,
1. Select nextval('myseq'), then use the nextval as the new id to
insert a new record.
2. Insert a new record, then do select currval('myseq') or select last_val
from myseq; supposed to be safe
3. use transaction to guarantee safety
On Tuesday 13 April 2004 16:43, Donald Fraser wrote:
> I am trying to build Postgres 7.4.2 from the source rpm on Red Hat Linux
> 7.1 2.96-98
While I do test builds on a Red Hat 7.3 compatible system, I do not do so on a
7.1 system. Sorry.
> I get the following error message:
> [EMAIL PROTECTED
Hello,
Currently I can get no more than 40k records/second to be copied
in to postgres. This is also the case when running multiple
cocurrent copy in commands from different connections. It
seems linear in that 1 process will copy in at 40k/s and 2
will copy in at about 20k/s, etc.
I need to kno
On Wed, Apr 14, 2004 at 14:44:57 +0100,
Paul Breen <[EMAIL PROTECTED]> wrote:
>
> The way we approached it was to do the replication ourselves at the
> application level. This isn't as hard as it sounds: you just open 2 db
> connections (1 to the master, 1 to the slave), start transactions on b
Has anyone used the XTG Data Modeller with postgres? If so, can you
comment on it's functionality?
Thanks
Jodi Kanter
--
___
Jodi L Kanter
BioInformatics Database Administrator
University of Virginia
(434) 924-2846
[EMAIL PRO
I hope it is OK to ask the question here.
Perl's DBI has the following function.
$rv = $dbh->last_insert_id($catalog, $schema, $table, $field);
"Returns a value 'identifying' the row just inserted, if possible."
I wonder what this $catalog is in this context. It's supposed to be
metadata, and
On Apr 14, 2004, at 10:53 AM, Ben Kim wrote:
I hope it is OK to ask the question here.
Perl's DBI has the following function.
$rv = $dbh->last_insert_id($catalog, $schema, $table, $field);
"Returns a value 'identifying' the row just inserted, if possible."
I wonder what this $catalog is in this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Perl's DBI has the following function.
>
> $rv = $dbh->last_insert_id($catalog, $schema, $table, $field);
> "Returns a value 'identifying' the row just inserted, if possible."
>
> I wonder what this $catalog is in this context. It's supposed to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Also, in perl DBI, the solutions all require executing at least
> 2 sql statements.
Nothing wrong with that.
> I initially hoped there'd be a way to get the oid or sequence number
> at the same time as executing an INSERT (one sql statement),
"Donald Fraser" <[EMAIL PROTECTED]> writes:
> 2) One of my queries does an ORDER BY on a column that is of type BOX.
> This query no longer runs and returns the following error message:
> ERROR: could not identify an ordering operator for type box
What are you expecting that to do? Boxes have no
14 matches
Mail list logo
