I'm getting ready to spend some time testing out the new replication server.
The documentation is sparse, so I'm wondering if there are any known bugs?
Also, is there a specific forum/list for discussion of the server?
Thanks ...
Bryan Ingram
> Hmm. Have you VACUUM ANALYZED the tables? If so, what do
> you get from
> these queries:
Tom, thanks for the reply, and here is all the info you asked for.
> select attname,attdisbursion,s.*
> from pg_statistic s, pg_attribute a, pg_class c
> where starelid = c.oid and attrelid = c.oid and
I'm trying to find the nearest locations to a certain point using 2 tables.
One contains the address and zipcodes of the locations and is about 2000
rows, the other contains zipcodes and lat, lon values and has about 1.4M
rows.
I've got indexes on the zip column of both tables and I just need to
Hello ..
I'm having trouble figuring out a good way to return my desired results from
the following table ...
Table= g_state_county_app
app_code | varchar() not null
state_code | int4 not null
county_code
A couple weeks back I wrote in with a few questions and comments asking
about the possibilities of creating a re-do log in Postgres for the purpose
of creating a Standby database. That is, a database that would be
reasonably current (within 5 minutes) and available to take over within one
minute
> It would seem about that the only currently viable technique for creating
> a standby database in case of a primary database failure is to ship output
> from pg_dump(all) to an awaiting postgres instance and reload them.
>
> I'm currently working on a few scripts to accomplish this which use cr
statement execution.)
3) Determine if the above two steps are sufficient to accurately recreate
the state of a database if the logs are re-applied to a backup.
Thanks,
Bryan Ingram
-Original Message-
From: Yury Don [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 21, 2000 11:29 AM
To:
I would like to create a long of all successful DML/DDL statements.
Has anyone accomplished this before? No need to reinvent the wheel ...
If not ..I'm wondering what the best approach might be.
I have looked at the tcop/postgres.c source, thinking I might start by
modifying some of the -dX ro