--- Devrim GUNDUZ [EMAIL PROTECTED] wrote:
Could you please tell us why integer datetimes
should be enabled in our
RPMs by default?
We are not sure that many people need it, also it's
easy for someone to
add this support using the SRPMs provided.
Consistent precision through the range
In postgresql 8.0, create table as ... statements
appear not to logged unless log_statement = 'all' in
postgresql.conf. We are trying to reduce noise in the
logs from pgAdminIII and phpPgAdmin, but we use a lot
of 'create table as ...' queries that need to be
logged, and their duration tracked.
--- Tom Lane [EMAIL PROTECTED] wrote:
Because almost nobody has complained about the lack
of it.
(I'm talking about actual field experience of there
being a
problem, not somebody objecting that it sounds like
a
feature worth having.)
It should also be pointed out that we are still
Can integer datetimes support be added to the PGDG
distributed RPMS for Fedora at the next version
requiring an initdb. I've attached a diff to the
specfile for 8.0.1.
Thanks, Murthy
--- /usr/src/redhat/SPECS/postgresql-8.0.1-2PGDG.spec
2005-02-22 18:04:50.0 -0500
+++
On Wednesday, April 07, 2004 1:26 AM Tom Lane wrote:
But to get back to the point of this discussion: to allow PG
to use raw devices instead of filesystems, we'd first have to do a ton of
portability work
...
[The following is said in a low, tentative voice :) ]
I wonder if writing the
I think you can get both benefits of multi-statement transactions for INSERT dumps
by doing subset copies ... without any changes in postgresql! The method I use is
developed for handling single table loads, but is still relatively painless even for
database dumps; however, it is limited to
db_quux -f - -Atnq $LogFile 21)
Cheers,
Murthy
-Original Message-
From: [EMAIL PROTECTED] on behalf of Murthy Kambhampaty
Sent: Fri 3/26/2004 3:30 PM
To: Naomi Walker; Tom Lane
Cc: Bruce Momjian; Tsirkin Evgeny; Mark M. Huber; [EMAIL PROTECTED]
Subject: Re: [Retrieved]RE: [ADMIN] backup
Thanks Tom and Reece for replying. It turns out that the
cryptolib/cryptsrc/random source combination I specified --
openssl/system/openssl -- was the problem; changing the combination to
openssl/builtin/openssl, solved the problem.
~/contrib/pgcrypto/Makefile snippet:
# either 'builtin',
After having initdb'd and started the server (gmake check said it passed all
93 tests), and doing a make; make install in pgcrypto, I tried creating the
pgcrytpo functions with
# psql -d template1 -f pgcrypto.sql
This produced a series of errors as follows:
2003-11-12 16:56:14.287480500 [9781]
If it's a bash script you could use:
#
SomeTable=Table you're about to create
TableTest=$(psql -d your new db -U its owner -ntc select relname from
pg_class where relname='$SomeTable')
[[ -n $TableTest ]] psql -d your new db -U its owner -nc drop
table $SomeTable
#
It's not quite in
IMHO, while point-in-time recovery would be great to have, there are many
applications that benefit from having online backup and recovery without
needing log roll-forward. For example, Oracle contrasts Full Database
Point-in-time Recovery, the feature mentioned by Bruce, with Tablespace
Point in
On Thursday, September 04, 2003 18:12, Bruce Momjian
[mailto:[EMAIL PROTECTED]
Murthy Kambhampaty wrote:
...
I assume you are contrasting _any_ point-in-time recovery to recover up
to the crash point, right?
Right.
Anyway, unfortunately, WAL doesn't contain enough information
to recover
without
Does version 7.3 provide a way to get VACUUM activity reports in the server
log (postmaster's stderr) without having them show up in the client's
stderr?
In 7.2, running vacuum quiet, i.e.,
/usr/local/pgsql/bin/vacuumdb -U postgres -q -a -z
logged vacuum activity to the server log. e.g.,
DEBUG:
I think its fair to say that the documentation is outdated on this subject,
becuase it had in mind a different definition of consistent snapshots.
See:
http://marc.theaimsgroup.com/?l=postgresql-adminw=2r=1s=LVM+snapshotsq=b
where Tom Lane and Peter Eisentraut agree that if your hardware or
On Monday, August 11, 2003 17:26, [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, August 11, 2003 17:26
To: [EMAIL PROTECTED]
Subject: Re: [ADMIN] Backup routine
In article [EMAIL PROTECTED],
Bruce Momjian [EMAIL PROTECTED]
There's an extensive discussion of doing file system level backups off an
LVM snapshot taken on a frozen XFS filesystem (XFS provides xfs_freeze
command which allows the sysadmin to freeze and unfreeze a given file system
at will). See
I think you'd benefit from a two-stage Rsync (this was discussed on this
list in the past few months):
1. Rsync the $PGDATA cluster from the hot server to the standby server,
with the postmaster running
2. Stop the postmaster and perform the same rsync again (this will take only
a few seconds on
While putting a test server (dual PIII 1GHz, 512M ram, ide single disk for
system and $PGDATA) under high load, I keep running into:
Mar 18 12:33:19 c257lx postgres[25277]: [6] NOTICE: ALTER TABLE / ADD
PRIMARY KEY will create implicit index 'test_pkey' for table 'test'
Mar 18 12:33:22 c257lx
Here's the script I use to mount a snapshot and rsync to a remote server;
postgresql is started and stopped on the remote server as part of the backup
procedure to make sure that the backup log contains any errors that might
show up. The restore strategy is to start the postmaster on the remote
I should have noted that unless $PGDATA/xlog is on the same LVM logical
volume as $PGDATA, the backups produced by the script I sent will be
useless.
-Original Message-
From: Murthy Kambhampaty [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2003 13:59
To: 'Matt Clark'; [EMAIL PROTECTED
Is there a way to do
pg_dump -h host1 -d db1 -t tbl1 -Fc | pg_restore -d db1 -h host2
selectively, when there are multiple tables named tbl1 in db1 on host1?
The following scenario clarifies the question:
I have two tables named exmpl_tbl, one in the schema public and the other
in the schema
Sorry for the chatter. I used gmake instead of make and passed all 89
tests. That's a new one on me.
With apologies,
Murthy
-Original Message-
From: Murthy Kambhampaty
Sent: Friday, December 13, 2002 15:58
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject
In bash, I use:
== script fragment ==
~!/bin/bash
$BackupDir=whereever
$LogFile=whichever
for db_name in $(/usr/local/pgsql/bin/psql -U postgres -d template1 -n -t -c
select datname from pg_database where datistemplate='f';);
do
/usr/local/pgsql/bin/pg_dump
The postgresql documentation states that in order to get a usable backup
from a filesystem dump (or copy) the database server must be shut down.
Moreover, Half-way measures such as disallowing all connections will not
work as there is always some buffering going on. For this reason it is also
not
As long as you are going to use pipes to do your load/unload or read from
one cluster, copy to another, why not go with:
/usr/local/pgsql/bin/psql -U -d -h \
-P format=unaligned -P fieldsep='\t' -P tuples_only \
-c select * from tab where yoo='hoo' |
There seems to be a bug in psql's -R option (and the -P recordsep= )
version. I find that whereas the following succeeds:
/usr/local/pgsql/bin/psql -U -d -h \
-P format=unaligned -P fieldsep='\t' -P tuples_only \
-c select * from tab where yoo='hoo' |
]
Sent: Tuesday, November 05, 2002 14:21
To: Murthy Kambhampaty
Cc: '[EMAIL PROTECTED]'
Subject: Re: [ADMIN] Bug in psql's -R option?
psql -R controls the record separator for query output, not COPY.
---
Murthy Kambhampaty
FYI, our signal 11 problem was caused by faulty cache memory on the RAID
controller.
-Original Message-
From: Eric L. Blevins [mailto:eblevins;insight.rr.com]
Sent: Thursday, October 31, 2002 11:16
To: [EMAIL PROTECTED]
Subject: Re: [ADMIN] Signal 11
From: Andrew Sullivan [EMAIL
The following appeared in the log this am, while running vacuumdb:
[13323] DEBUG: ReceiveSharedInvalidMessages: cache state reset
[25461] DEBUG: SendSharedInvalidMessage: SI buffer overflow
[13322] DEBUG: ReceiveSharedInvalidMessages: cache state reset
[13323] DEBUG:
29 matches
Mail list logo
