Philip Hallstrom [EMAIL PROTECTED] writes:
I took a look around and was unable to find a Perl DBI driver for
PostgreSQL... does one exist that I'm missing?
DBD-Pg, at rev 0.93 last I looked at the CPAN archives. For some
bizarre reason it's not listed on the index page about DBI
Hi all,
I made an update (pg_dump) from 6.5 to 7.0 (i686-pc-linux-gnu, compiled
by gcc egcs-2.91.66),
I created an index on column gmkg_tl by doing:
create index ix_flurst_gmkg_tl_ix on flurstueck using btree (gmkg_tl
bpchar_ops);
gmkg_tl is char(16).
When I do a
select * from flurstueck where
Hello pgsql-general,
I have a problem. I want to make the company I work to go from Informix Online
and SCO to PostgreSQL + Linux and I want this transition to be made, if
it possible, very smooth.
Anybody from this list make this transition and found or made some tools to
make import from
On Tue, 30 May 2000, Dana Eckart wrote:
Things work fine with the authorization type in pg_hba.conf set to "trust".
However, when I try to use either "crypt" or "password" psql fails to
authenticate either the postgresql super-user (mylocal in my case) or any
other non-privelegded user.
In
It means Postgres can do a reliable backup (a consistent snapshot) of a
database without shutting down the database.
What you are asking for is replication, which is not easy to implement,
and almost damn impossible to get it RIGHT. (*curse at both Sybase and
Oracle replication servers*). (i.e.
I have now a program that works aginst a Postgresql. I have a wrapper
class that gets the query.
The sequence is like this in Postgresql
res=PQexec(conn, query);
value = PQgetvalue(res, tuple, col);
The problem is col because you don't know what kind of colunm the
program send into this
See archives of this mailing list.
WAL is write-ahead logging, more conventional way of assuring atomicity.
(I.E. before a transaction is written to database, it is written to
transaction log, which can be replayed). Replication can be achieved by
streaming transaction log toyour replicated
Thanks a lot.
Now, what is WAL?
When is it scheduled for implementation?
It means Postgres can do a reliable backup (a consistent snapshot) of a
database without shutting down the database.
What you are asking for is replication, which is not easy to implement,
and almost damn impossible to
Alex Pilosov wrote:
http://networkdna.com/database/index.html mentions that PostgreSQL is
capable of "Online backup". What does that exactly mean?
It means Postgres can do a reliable backup (a consistent snapshot) of a
database without shutting down the database.
Hmmm. My backup
Alex Pilosov wrote:
http://networkdna.com/database/index.html mentions that PostgreSQL is
capable of "Online backup". What does that exactly mean?
It means Postgres can do a reliable backup (a consistent snapshot) of a
database without shutting down the database.
Hmmm. My
Bruce Momjian wrote:
Alex Pilosov wrote:
http://networkdna.com/database/index.html mentions that PostgreSQL is
capable of "Online backup". What does that exactly mean?
It means Postgres can do a reliable backup (a consistent snapshot) of a
database without shutting down
On Wed, 31 May 2000, Ed Loehr wrote:
# Hmmm. My backup procedure, based on earlier discussions in this group,
# involves blocking all write-access during a pg_dump. That is
# effectively shutting down the database from my perspective. Is there a
# quicker way to take a consistent snapshot
No, that's now what he said. You can backup the database while it's still
being used (the pg_dmp runs in a transaction) but you still can't vacuum a
database while it's in use. Vacuuming is more along the lines of a defrag,
it updates the indexes and maintains stats.
At 12:16 PM 5/31/00, Ed
Charles Tassell wrote:
No, that's now what he said. You can backup the database while it's still
being used (the pg_dmp runs in a transaction) but you still can't vacuum a
database while it's in use. Vacuuming is more along the lines of a defrag,
it updates the indexes and maintains
Hello out there,
I'm having a problem with a production server. Actually, there are two
problems. The semi-trivial problem is that Postgres won't die using the
service mechanism. As root, I "service postgres stop" and then "service
postgres start" after a reasonable wait. The restart
Jerry Lynde wrote:
I'm having a problem with a production server. Actually, there are two
problems. The semi-trivial problem is that Postgres won't die using the
service mechanism. As root, I "service postgres stop" and then "service
postgres start" after a reasonable wait. The
Jerry Lynde wrote:
Hello out there,
I'm having a problem with a production server. Actually, there are two
problems. The semi-trivial problem is that Postgres won't die using the
service mechanism. As root, I "service postgres stop" and then "service
postgres start" after a
Not sure this belongs in the FAQ. Seems more of a web page thing.
Due to a recent thread started on pgsql-hackers, I'm posting this to the
lists. Vince is planning on putting in appropriate links for some of
this, and, Bruce, can we maybe put it into the FAQ?
I'm not an English major,
We support servers on NT, but not on Win95/98. Cygwin supports both,
What's the performance like?
NT doesn't do forks well and Postgres uses forks right?
Cheerio,
Link.
mikeo wrote:
hi,
in oracle you would use these two cursors to determine who was connected and
what they were doing.
select distinct s.sid sid, s.serial# serial, s.status status, osuser, spid ,
count(o.sid) counter, s.username username, s.program program, sql_address
from v$session s,
hi,
in oracle you would use these two cursors to determine who was connected and
what they were doing.
select distinct s.sid sid, s.serial# serial, s.status status, osuser, spid ,
count(o.sid) counter, s.username username, s.program program, sql_address
from v$session s, v$open_cursor o,
I have sent off the first draft of my book to the publisher for review.
Since last week, I have doubled the size of the Administration chapter(20),
and updated all the SQL output to match the 7.0 format.
The books is accessible at:
http://www.postgresql.org/docs/awbook.html
Comments
22 matches
Mail list logo
