"Does the server log say anything about broken
connections or client not responding?"
Nope, no errors in server log, just high I/O and no free slots remaining.
We are thinking of adding more RAM to the server what should speed up the
queries..
--
Best regards,
Viktor
Hi
I have postgresql 9.2 installed on red hat linux 6.4 . I need to generate uuids
using the uuid_generate_v4() function.
select * from pg_available_extensions does not list this extension. The only
extension that is available is plpgsql.
I find uuid libraries, libuuid.so.1 and libuuid.so.1.3
Hi,
I ran the following command on my server:
yum search postgresql
this listed postgresql92-contrib.x86_64 package.
I tried to do a yum install of this package but that threw an error that it
requires libossp-uuid.so.16()(64bit).
[root@perf277 ~]# yum install postgresql92-contrib.x8
Hi - I am trying to build a search engine where frequency of a term in the
search document is very important and I need ts_vector to be able to support
more than 256 positions per lexeme (up to 2000 at least). Does anyone know
of a workaround to this limit or how I could build one?
Thanks in adva
I built a new server running centos 6.4 and postgresql 8.4. I backed up all the
databases from the old server running fedora and postgresql 8.1 using this
script.
#!/bin/bash
# Backup all Postgresql databases
# Location of the backup logfile.
logfile="/var/lib/pgsql/backups/logs/pg_back.log"
#
Thanks for your reply.
---> You should update to 9.1.9.
Recently I updated to 9.1.5. I will do in near future.
--> How are you doing this restore? Is it from a dump? Are you using or
could you use custom format?
I am pg_restore using for restoring the backup which created using pg_dump.
-
Thanks for your reply.
---> You should update to a more current minor release.
Recently I updated to 9.1.5. I will do in near future.
--> You need to provide more information on how you backed up, how you
are restoring, and what the bottleneck seems to be.
I am pg_restore using for restoring
it sounds like you are missing the contrib code.
if you built from source you need to go to the contrib directory and run make,
make install.
if you installed from a package you need to install the appropriate contrib
package.
reiner
sent by smoke signals at great danger to my self.
On 1
Can you use '-v' with pg_dumpall and output to the log file? That might
help. Likely something is not right with the individual pg_dump processes
that work inside the pg_dumpall.
Payal Singh,
OmniTi Computer Consulting Inc.
Junior Database Architect,
Phone: 240.646.0770 x 253
On Thu, Oct 10, 201
I also realized that during the restore any database with latin1 encoding is
not created at all
psql:pgdbs:167: ERROR: encoding LATIN1 does not match locale en_US.UTF-8
DETAIL: The chosen LC_CTYPE setting requires encoding UTF8.
About half my databases are latin1.
My problem is now two fold, h
On 10/10/2013 01:17 PM, Marc Fromm wrote:
I built a new server running centos 6.4 and postgresql 8.4. I backed
up all the databases from the old server running fedora and postgresql
8.1 using this script.
*#!/bin/bash*
*# Backup all Postgresql databases*
**
*# Location of the backup logfi
On the old system running 8.1 I am executing the pg_dumpall command as shown in
the script. I then copy the file to the new server running 8.4 and run this
command "psql -U postgres -f postgresql-all-10-10-2013_04-07-databases postgres"
The log is reporting
database name_of_database does not exi
After the last database is created there is a failed connection attempt to the
first database, which never gets created since it is latin1 encoding.
psql:pgdbs:229: ERROR: database "wsasea_db" does not exist
CREATE DATABASE
psql:pgdbs:233: \connect: FATAL: database "awarding_letter_count" does n
I need to convert a bunch of my databases to utf8 before I can migrate them to
postgresql 8.4. Is there a command that during the pg_dumpall process the
encoding can be changed from latin1 to utf8?
This is the error I get when migrating the databases from 8.1 to a machine
running 8.4
psql:pgdbs
I needed both UTF8 and Latin-1. I accomplished this by initdb with the LOCALE
set to C. That lets me create dbs "with template0 encoding='Latin-1'" as well
as "encoding=UTF8," FWIW...
Original message
From: Marc Fromm
Date: 10/10/2013 5:39 PM (GMT-06:00)
To: pgsql-admin@po
15 matches
Mail list logo
