> Joel Burton suggested the rserv utility. I don't know how well it would
> work over a wide network.
It should work well over a WAN for what it can do. However, that is
async one-way replication, which was not your initial requirement.
Of course, requirements sometimes adjust in the face of rea
You probably already thought of this - but - why not just set up a
centralized server and have each office interact to the db via a web
interface. Let your application enforce security (apacheSSL, use db for
user auth) and to prevent two users from editing the same record
simultaneously.
-r
> Okay, you're right. I just updated my Ghostscript to 7.00 (just out) and it
> produced very nice PDFs. I can upload them somewhere if you give me an FTP
> address.
Just mail them to me and I'll post them for you. ps2pdf seems to do a
nice (simple) job from the 5.50 version I'm running, so pre
On Fri, Apr 20, 2001 at 04:53:43PM -0700, G. Anthony Reina wrote:
> Nathan Myers wrote:
>
> > Does the replication have to be reliable? Are you equipped to
> > reconcile databases that have got out of sync, when it's not?
> > Will the different labs ever try to update the same existing
> > re
Nathan Meyers wrote:
> Does the replication have to be reliable? Are you equipped to
> reconcile databases that have got out of sync, if not? Will the
> different labs ever try to update the same existing record, or
> insert conflicting (unique-key) records?
>
(1) Yes, of course. (2) Willing-
Okay, you're right. I just updated my Ghostscript to 7.00 (just out) and it
produced very nice PDFs. I can upload them somewhere if you give me an FTP
address.
Ken Hirsch
- Original Message -
From: "Bruce Momjian" <[EMAIL PROTECTED]>
To: "Ken Hirsch" <[EMAIL PROTECTED]>
Cc: <[EMAIL PRO
> Reliable WAN replication is harder. Most of the proprietary database
> companies will tell you they can do it, but their customers will tell
> you they can't.
This comment is great.
--
Bruce Momjian| http://candle.pha.pa.us
[EMAIL PROTECTED] |
On Fri, Apr 20, 2001 at 03:33:38PM -0700, G. Anthony Reina wrote:
> We use Postgres 7.0.3 to store data for our scientific research. We have
> two other labs in St. Louis, MO and Tempe, AZ. I'd like to see if
> there's a way for them to mirror our database. They would be able to
> update our datab
We use Postgres 7.0.3 to store data for our scientific research. We have
two other labs in St. Louis, MO and Tempe, AZ. I'd like to see if
there's a way for them to mirror our database. They would be able to
update our database when they received new results and we would be able
to update theirs.
> > I modified and compiled *but did not check into cvs* build.c to get nice
> > references for the new Developer's and Reference docs.
> I never had buildmenu.c checked in. What did you modify? I didn't
> see anything noticable. Anyway unless new filetypes are being introduced
> you only need
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Remember one idea is for index scans to automatically update the expired
> > flag in the index bitfields when they check the heap tuple.
>
> There is no such flag, and I'm not planning to add one before I fix
> statistics ;-)
>
> There are a number
> A different approach that's been discussed on pghackers is to make use
> of btree indexes for columns that have such indexes: we could scan the
> indexes to visit all the column values in sorted order. I have rejected
> that approach because (a) it doesn't help for columns without a suitable
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Remember one idea is for index scans to automatically update the expired
> flag in the index bitfields when they check the heap tuple.
There is no such flag, and I'm not planning to add one before I fix
statistics ;-)
There are a number of things that'
On Fri, 20 Apr 2001, Thomas Lockhart wrote:
> Hi Vince. I've put the 7.1 docs on the web site in the appropriate
> place. Nice auto-generating web page stuff btw.
>
> I modified and compiled *but did not check into cvs* build.c to get nice
> references for the new Developer's and Reference docs.
On Sat, 21 Apr 2001, Philip Warner wrote:
> At 11:29 20/04/01 -0500, Jan Wieck wrote:
> >Philip Warner wrote:
> >> At 08:42 19/04/01 -0500, Jan Wieck wrote:
> >> >and the required
> >> >feature to correctly restore the tgconstrrelid is already in
> >> >the backend, so pg_dump sh
Hi Vince. I've put the 7.1 docs on the web site in the appropriate
place. Nice auto-generating web page stuff btw.
I modified and compiled *but did not check into cvs* build.c to get nice
references for the new Developer's and Reference docs.
OK? If you want to inspect the changes, then commit
Peter Eisentraut <[EMAIL PROTECTED]> writes:
>> Alternatively, since you really only need two bits per privilege,
>> perhaps a pair of BIT (VARYING?) fields would be a more effective
>> approach. BIT VARYING would have the nice property that adding a new
>> privilege type doesn't force initdb.
>
At 11:29 20/04/01 -0500, Jan Wieck wrote:
>Philip Warner wrote:
>> At 08:42 19/04/01 -0500, Jan Wieck wrote:
>> >and the required
>> >feature to correctly restore the tgconstrrelid is already in
>> >the backend, so pg_dump should make use of it
>>
>> No problem there - just tell
Philip Warner wrote:
> At 08:42 19/04/01 -0500, Jan Wieck wrote:
> [...]
> >and the required
> >feature to correctly restore the tgconstrrelid is already in
> >the backend, so pg_dump should make use of it
>
> No problem there - just tell me how...
Add a "FROM " after the
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> Tom Lane writes:
>> 2. The M boundary values of an equi-depth histogram, ie, the values that
>> divide the data distribution into equal-population sets. For example, if
>> M is 3 this would consist of the min, median, and max values.
> Why not model
Tom Lane writes:
> Peter Eisentraut <[EMAIL PROTECTED]> writes:
> > pg_privilege (
> > priobj oid, -- oid of table, column, function, etc.
> > prigrantor oid, -- user who granted the privilege
> > prigrantee oid, -- user who owns the privilege
>
> W
Tom Lane writes:
> 2. The M boundary values of an equi-depth histogram, ie, the values that
> divide the data distribution into equal-population sets. For example, if
> M is 3 this would consist of the min, median, and max values.
Why not model that data in a normal distribution (or some other
Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
>> But you don't really need to look at the index (if it even exists
>> at the time you do the ANALYZE). The extent to which the data is
>> ordered in the table is a property of the table, not the index.
> Think compound, ascending, descending
> But you don't really need to look at the index (if it even exists
> at the time you do the ANALYZE). The extent to which the data is
> ordered in the table is a property of the table, not the index.
Think compound, ascending, descending and functional index.
The (let's call it) cluster statis
24 matches
Mail list logo
