I have a table that users can update if the data is old. Once a day I
update every entry in the table. However I get primary key violations
occasionally which it seems a user inserted into the table while the bulk
insert is going on.
The following is the procedure I use for updating the entire t
I have started testing 8.3.3 and investigating how autovacuum can replace
most or all of our cron maintenance tasks.
While looking at autovacuum logs I see messages for vacuum come in pairs:
Jul 25 02:31:19 iprobe001 postgres[25488]: [4-1] LOG: automatic vacuum of
table "issp.iprobe001.probe_tra
If the databases are on the same machine, I could see creating a template
database and then use:
createdb -T templateName newDbName
It will create the new db exactly like the template. I think createdb does
this by default using the database template1 as the template.
My databases are all on
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane
Sent: Thursday, August 09, 2007 2:14 PM
To: Woody Woodring
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Bytea question with \208
"Woody Woodring" <[EMAIL PROTECTED]> writes:
Could someone explain why \208 is not a valid syntax for bytea?
I am getting the following:
test=> select E'\\207'::bytea;
bytea
---
\207
(1 row)
test=> select E'\\208'::bytea;
ERROR: invalid input syntax for type bytea
test=> select E'\\209'::bytea;
ERROR: invalid input syntax for type
I have a table in our DB that functions as a queue with a SERIAL column for
its primary key. At 4am this weekend I started getting the error:
ERROR: integer out of range
Which was attributed to the sequence incrementing past the size of the int4
serial column after several years of operation.
I am wondering if there is a proper procedure for shutting down the
warm_standby server (8.2.4)? I am using pg_standby as my restore script in
my testing:
[EMAIL PROTECTED] cat recovery.conf
restore_command = 'pg_standby -m -d -s 5 -w 0 -t /tmp/pgsql.trigger.5432
/usr/local2/pg_archive %f %p 2>>
Szabo
Sent: Wednesday, June 06, 2007 1:33 PM
To: Woody Woodring
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] String trim function - possible bug?
On Wed, 6 Jun 2007, Woody Woodring wrote:
> I am seeing weirdness using the trim function on a string:
>
> This works as expected:
I am seeing weirdness using the trim function on a string:
This works as expected:
SELECT 'dhct:bn', trim(leading 'dhct:' from 'dhct:bn');
?column? | ltrim
--+---
dhct:bn | bn
(1 row)
However it fails for these cases:
SELECT 'dhct:dn', trim(leading 'dhct:' from 'dhct:dn');
?colu
Is there a sql command to print out which database I am connected to?
I am using "psql -f sqlFile" in a sh script to up date tables on multiple
databases. I would like to have the sqlFile display the db name so I would
know which output lines go with each db without having to count the output
lin
Which Sunday? Could you have been bitten by some DST time shift? There
were 2 1ams a couple of weeks ago.
Woody
IGLASS Networks
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jeff Davis
Sent: Tuesday, November 07, 2006 5:38 PM
To: Tom Lane
Cc: pgsql-g
We use the pg_services.conf file.
http://www.postgresql.org/docs/8.1/static/libpq-pgservice.html
In the file you can point the alias to whatever db you
want. To connect:
[bash]$ PGSERIVCE=dbname psql
Woody
IGLASS Networks
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf O
Here is their web page:
http://postgis.refractions.net/
I am probably not the best to answer how it is used because
we use it just to allow index on spatial data (coordinates). You may ask
on the postgis mailing list.
Woody
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
I am running into this issue as well. I am
upgrading from 7.4.X to 8.1.4. My databases were "ASCII" encoded in
7.4.X
I am editing the dumps to remove the non-UTF8
characters, but you could also create your new db with "ASCII" encoding and it
should import fine.
Hope this helps,
Woody
Did you analyze after you imported the dump?
Woody
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Brain
Sent: Friday, February 03, 2006 10:03 AM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Postgres 7.3.2 -> 8.1.2 upgrade performance issue
You can use the "adduser" command to create the postgres user on your linux
box. I use Uid:26 Gid:100, but I don't know that it matters.
Woody
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ElayaRaja S
Sent: Thursday, April 28, 2005 9:19 AM
To: pgsql-ge
I make the changes into the pg_hba.conf and do a kill -HUP 'PID' for
postgres to reread the file. The pid number can be found in the
~postgres/data/postmaster.pid file
Woody
IGLASS Networks
www.iglass.net
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
17 matches
Mail list logo