James Lewis wrote:
> Does anyone have any suggestions for a way to keep 2 databases in sync?
>
> Ideally updates need to be made to both... this can't be too uncommon a
> requirement. any kind of HA would need it
No. The way HA works is that the system is made in such a way that you
ca
Jigishu P Bhatt wrote:
> I am developing an Information Management System. I am using
> PgAccess(0.98.5) as
> front end. The backend is PostgreSQL-6.5.2 and OS is Red Hat Linux
> 6.1, on
> Intel P-II 350 MHz connected with LAN. I have installed them using RPM
> of
> Linux. I have learned some
A while ago it was being held that the Postgres large object data type
was too new and not sufficiently tested and mature to be used in a
production environment. I am about to deploy a little database that
involves storing large-ish text files (20-500k) which could be either done
as large objects
Hello all,
In my quest to learn PG and SQL programming, I have
created tables in a database "foo". I am able to
insert, select, etc just fine, but when I use "\dt" to
show them they don't appear. They ARE listed in the
system table "pg_tables", however.
I have also tried to createdb "test1" aft
Webb Sprague wrote:
>
> Hello all,
>
> In my quest to learn PG and SQL programming, I have
> created tables in a database "foo". I am able to
> insert, select, etc just fine, but when I use "\dt" to
> show them they don't appear. They ARE listed in the
> system table "pg_tables", however.
This
Can anyone tell me what the following two messages mean? They are
from 6.5.3.
thanks,
--titus
NOTICE: equal: don't know whether nodes of type 719 are equal
NOTICE: LockReleaseAll: xid loop detected, giving up
--
Titus Brown, [EMAIL PROTECTED]
On Sun, 16 Apr 2000, Frank Joerdens wrote:
> A while ago it was being held that the Postgres large object data type
> was too new and not sufficiently tested and mature to be used in a
> production environment. I am about to deploy a little database that
> involves storing large-ish text files (20
On Sun, 16 Apr 2000, you wrote:
> There are some programs out there to dump large objects and I've been playing
> with one. It's worked well so far. You can get it at
> ftp://ftp2.zf.jcu.cz/zakkr/pg/
>
> ---
>
> file not found...
Correction:
ftp://ftp2.zf.jcu.cz/users/zakkr/pg/
Frank,
I don't know about varbinary. The 8k limit is expected to disappear in
version 7.1. The strategy to do this is known as TOAST. You might search the
archives for more details if you want them.
John Henderson
-Original Message-
From: Franck Martin <[EMAIL PROTECTED]>
To: [EMAIL PROTE
Hi,
It seems that the issue with large objects is "Why do you want the info in a
database?"
It seems to me that the point of a database is its ability to order and
relate data. If you want to retrieve the "large-ish text files" based on
their content then I think you need to have the files in the
At 01:23 PM 14-04-2000 -0400, Bruce Momjian wrote:
>
>> Perhaps its time for the two functions to be separated - controlled by an
>> option?
>> Perhaps VACUUM STATONLY could collect stats, not lock table and not reclaim
>> space.
>
>Makes sense.
Actually it may be more logical to have
VACUUM
Well I'm currently using the file system for large files. However because
of that I can see a few reasons why people might want to use Postgresql to
handle them. Others can probably mention more.
Using Pg to handle large stuff makes more consistent overall and it's
easier for you to handle except
Hola:
Una opinión sobre el uso de imágenes en blobs.
Alguien tiene experiencias al respecto?
Saludos,
Roberto Andrade Fonseca
[EMAIL PROTECTED]
-- Forwarded message --
Date: Mon, 17 Apr 2000 09:40:47 +0800
From: Lincoln Yeoh <[EMAIL PROTECTED]>
To: John Henderson <[EMAIL PROTE
> A while ago it was being held that the Postgres large object data type
> was too new and not sufficiently tested and mature to be used in a
> production environment. I am about to deploy a little database that
> involves storing large-ish text files (20-500k) which could be either done
> as larg
IIRC, certain kinds of pg errors trigger exceptions that can only be caught
with an eval wrapper. Not sure, but the DBD::Pg module may just be
parroting the bail-out behavior of the backend.
Regards,
Ed Loehr
Jeffrey wrote:
>
> Hi,
>
> I am having trouble catching errors from postgress. I am
-> It seems that the issue with large objects is "Why do you want the info in a
-> database?"
To organize them, of course.
-> It seems to me that the point of a database is its ability to order and
-> relate data. If you want to retrieve the "large-ish text files" based on
-> their content then
Peter Eisentraut wrote:
>
> Haroldo Stenger writes:
>
> > I seems that other DBMSs, don't care about erroneous statements within
> > a transaction. Now, I have several paths to follow: 1) Hacking the
> > backend ;-)
>
> If you're really brave you can try this change in
> backend/tcop/postgres.c
17 matches
Mail list logo
