On Wednesday 10 May 2017 17:13:50 Ron Ben wrote:
> Not possible
> https://www.postgresql.org/download/linux/debian/
>
> To upgrade I do: apt-get install postgresql-9.3
> There is no way to "roll back" from here.
> I can not choose which version to install, it install the latest version
> packed
On Thursday 04 May 2017 14:47:54 John R Pierce wrote:
> On 5/4/2017 2:28 PM, Alan Hodgson wrote:
> > On Thursday 04 May 2017 14:21:00 John R Pierce wrote:
> >> or EBS, and I've heard from more than a few people that EBS can be
> >> something of a sand trap.
>
On Thursday 04 May 2017 14:21:00 John R Pierce wrote:
> or EBS, and I've heard from more than a few people that EBS can be
> something of a sand trap.
>
Sorry for following up off-topic, but EBS has actually improved considerably
in the last few years. You can get guaranteed (and very high) IOPS
> On Fri, Apr 21, 2017 at 12:40 PM, Edson Lidorio
>
> wrote:
> > Hi,
> > There was a disaster in my development note. I was able to recover the
> > data folder. PostgreSQL 9.6.2, was installed in Centos 7.
> >
> > Here are the procedures I'm trying to initialize Postgresql for me to do a
> > bac
On Friday 17 February 2017 18:18:20 Michael Tyson wrote:
> postgres=# \q
> pi@raspi ~ $ sudo -u postgres psql testdb
> psql: FATAL: database "testdb" does not exist
> pi@raspi ~ $ sudo -u postgres createdb testdb
> createdb: database creation failed: ERROR: duplicate key value violates
> unique c
On Tuesday 25 October 2016 17:08:26 t.dalpo...@gmail.com wrote:
> Hi,
> let's suppose I have:
> - a primary server with its own local archive location, configured for
> continuous archiving
> - a standby server without archive.
> These servers are configured for Sync streaming replication .
> L
On Tuesday 21 June 2016 19:34:18 Ramalingam, Sankarakumar wrote:
> Hi I have my standby (streaming replication) down due to missing wal files.
> You would see the same error in the logs stating "cannot find the wal file
> ..." What is the best way to get it going so that when we switch between
> st
On Tuesday, May 31, 2016 10:13:14 AM Jim Longwill wrote:
> I am trying to setup a 2nd, identical, db server (M2) for development
> and I've run into a problem with starting up the 2nd Postgres installation.
>
> Here's what I've done:
>1) did a 'clone' of 1st (production) machine M1 (so both ma
On Friday, May 27, 2016 05:32:08 PM Melvin Davidson wrote:
> Well, Slony certainly will do the trick.
> Keep in mind you will need to do schema only first to the slave.
> You set up replication from the old server with the db on the new server as
> the slave. Then you initiate replication. It will
On Monday, May 16, 2016 03:41:23 PM David G. Johnston wrote:
> I have a psql script that obtains data via the \copy command and loads it
> into a temporary table. Additional work is performed possibly generating
> additional temporary tables but never any "real" tables. Then the script
> outputs,
On Wednesday, April 06, 2016 10:33:16 AM Lars Arvidson wrote:
> > I'd guess it's probably more like option 3 - Glusterfs ate my database.
>
> Hi, thanks for your reply!
> We do archive logs on a distributed Glusterfs volume in case the streaming
> replication gets too far behind and the transactio
On Tuesday, April 05, 2016 12:55:04 PM Lars Arvidson wrote:
> Is there something I missed in the switchover or could this be a bug?
>
I'd guess it's probably more like option 3 - Glusterfs ate my database.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes t
On Tuesday, December 15, 2015 11:26:40 PM zh1029 wrote:
> Hi,
> It seems low performance PostgreSQL(9.3.6) while writing data to glusterFS
> distributed file system. libgfapi is provide since GlusterFS version 3.4 to
> avoid kernel visits/data copy which can improve its performance. But I
> didn'
On Wednesday, December 09, 2015 07:55:09 AM FattahRozzaq wrote:
> archive_mode = on
> archive_command = 'cp -i %p /home/postgres/archive/master/%f'
>
>
> The WAL archive folder is at /home/postgres/archive/master/, right?
> This directory consumes around 750GB of Disk-1.
> Each segment in the /ho
On Wednesday, August 26, 2015 08:25:02 PM Cory Tucker wrote:
> What settings would you recommend? Also, it just occurred to me that I
> should try to disable/drop all indexes (especially since they will be
> recreated) later so that those are not updated in the process.
Don't drop the indexes you
On Wednesday, December 17, 2014 01:55:46 PM Thomas Kellerer wrote:
> Albe Laurenz schrieb am 17.12.2014 um 11:07:
> > and the performance will be worse than reading files from the file system.
>
> There is a Microsoft research [1] (from 2006) which tested this "myth" using
> SQL Server. It showed
On Friday, October 03, 2014 11:24:31 AM Israel Brewster wrote:
> I have a Postgresql 9.3.5 server running on CentOS 6.5. In looking at some
> stats today, I saw that it was handling about 4-5 transactions/second
> (according to the SELECT sum(xact_commit+xact_rollback) FROM
> pg_stat_database; quer
On Tuesday, September 23, 2014 02:05:48 PM Nick Guenther wrote:
> I uninstalled all the postgres subpackages and rebuilt them from
> ports, and ended up with an identical plpython2.so, which has these
> checksums:
> SHA256 (/usr/local/lib/postgresql/plpython2.so) =
> 8c7ff6358d9bf0db342e3aca1762cd7
On Monday, September 22, 2014 11:17:05 AM Luke Coldiron wrote:
> The actual size of the table is around 33 MB.
> The myFunc function is called every 2.5 seconds and the wasUpdated function
> every 2 seconds by separate processes. I realize that running a FULL VACUUM
> or CLUSTER command on the tabl
On Friday, August 29, 2014 04:14:35 AM Yogesh. Sharma wrote:
> Dear David,
>
> > Are you currently using PostgreSQL?
>
> Currently we are using PostgreSQL 8.1.18 version on RHEL 5.8.
> Now we plan to update this to PostgreSQL 9.0 version with RHEL6.5. As in
> verion 9.0 I found least Compatibili
On Monday, July 21, 2014 09:05:18 PM Karthik Iyer wrote:
> Hello,
>
> We are planning to upgrade Postgres from 9.0 to 9.3. Was wondering
> if there are any serious changes that I have to look out for
> (syntax/datatypes changes) so that my code does not break.
>
http://www.postgresql.org/do
On Thursday, June 19, 2014 10:21:56 AM Andy Colson wrote:
> On 06/16/2014 08:10 PM, sunpeng wrote:
> > We have many small size(most fixed size) images, how to store them? There
> > are two options: 1. Store images in folders, managed by os file system,
> > only store path in postgresql 2. Store ima
On Monday, June 09, 2014 08:05:41 PM Khangelani Gama wrote:
> Hi All
>
> I would like to re-post the problem we have. The secondary server ran out
> the disc space due the replication problem (Connection Time out).
The secondary server would not (could not) run out of drive space due to a
proble
On Monday, June 09, 2014 04:28:53 PM Khangelani Gama wrote:
> Please help me with this, my secondary server shows a replication problem.
> It stopped at the file called *00054BAF00AF …*then from here
> primary server kept on sending walfiles, until the walfiles used up the
> disc space
On Wednesday, June 04, 2014 10:49:18 PM sramay wrote:
> relation "public.file_attachments" does not exist
.. is almost certainly not a size problem. What does your PostgreSQL log say?
I suspect your app is connecting to the wrong database.
--
Sent via pgsql-general mailing list (pgsql-general@
On Monday, April 14, 2014 09:13:51 AM Steve Clark wrote:
> How did you deal with binaries and libraries, as well as third party apps
> like perl modules or php/apache modules?
The 8.4 library package usually ends up installed to satisfy other package
requirements.
Binaries get handled through th
On Wednesday, April 09, 2014 09:02:02 PM Brent Wood wrote:
> Given the likely respective numbers of each OS actually out there, I'd
> suggests BSD is very over-represented in the high uptime list which is
> suggestive.
Suggestive of ... sysadmins who don't do kernel updates?
--
Sent via pgsql-
On Thursday, April 03, 2014 02:48:03 PM Steven Schlansker wrote:
> On Apr 2, 2014, at 3:08 PM, Jacob Scott wrote:
> • pg_start_backup
> • Take a filesystem snapshot (of a volume containing postgres data but
> not
> pg_xlog) • pg_stop_backup
> • pg_ctl stop
> • Bring a new
On Tuesday, March 25, 2014 02:56:48 PM Frank Foerster wrote:
> Hi,
>
> we are currently in the process of upgrading a production/live 1 TB
> database from 9.2 to 9.3 via pg_dump, which is quite a lengthy process.
>
> Fortunately we have a capable spare-server so we can restore into a clean,
> fre
On Thursday, October 24, 2013 11:13:34 PM Jayadevan wrote:
> Alan Hodgson wrote
>
> > That's basically what warm standby's do, isn't it? As long as they keep
> > recovery open it should work.
>
> A warn standby will be almost in sync with the primary, righ
On Thursday, October 24, 2013 11:31:38 AM John R Pierce wrote:
> On 10/24/2013 9:47 AM, Jeff Janes wrote:
> > I restore from my base backup plus WAL quite often. It is how I get a
> > fresh dev or test instance when I want one. (It is also how I have
> > confidence that everything is working well
On Thursday, June 20, 2013 07:52:21 AM Merlin Moncure wrote:
> OP needs to explore use of connection pooler, in particular pgbouncer.
> Anyways none of this explains why the server is actually crashing.
It might be hitting file descriptor limits. I didn't dig into the earlier part
of this thread
On Wednesday, January 23, 2013 09:10:40 AM Ian Harding wrote:
> The System:
>
> Linux beta 2.6.32-279.19.1.el6.x86_64 #1 SMP Wed Dec 19 07:05:20 UTC 2012
> x86_64 x86_64 x86_64 GNU/Linux
>
That looks like a CentOS 6 system.
Go to http://yum.postgresql.org/repopackages.php
Find the repo appropr
On Monday, January 21, 2013 08:40:05 PM bhanu udaya wrote:
> Hello,Thanks alot for all your replies. I tried all settings suggested, it
> did not work. pg_restore is very slow. It does not come out less than 1 1/2
> hour. Can you please let me know the procedure for Template. Will it
> restore the
On Wednesday, December 05, 2012 02:44:39 AM Edson Richter wrote:
> Sort (cost=11938.72..11938.74 rows=91 width=93)
>Sort Key: t0.nome
>-> Nested Loop (cost=0.00..11938.42 rows=91 width=93)
> -> Nested Loop (cost=0.00..11935.19 rows=91 width=85)
>-> Seq Scan on
On Monday, November 05, 2012 05:15:41 AM salah jubeh wrote:
> Hello,
>
> I have the following scenario, I would like to upgrade a database server
> from 8.3 to 9.1. The upgrade includes also a hardware upgrade.
>
>
> I would like to have the following
>
> 1. Make sure that the upgraded server a
On Monday, October 22, 2012 05:55:07 PM Nikolas Everett wrote:
> I was just looking at
> http://www.postgresql.org/docs/devel/static/release-9-2.html and it
> mentioned that a dump/reload cycle was required to upgrade from a previous
> release. I just got done telling some of my coworkers that PG
> is it that you want?
> I've come across a few mentions of Heartbeat being used for PostgreSQL
> failover, do have any links to more information about this?
If you're going to use Heartbeat on a 2-server setup, you should use DRBD for
the replication, not the PostgreSQL replication. DRBD basical
On Monday, October 01, 2012 03:10:43 PM Shaun Thomas wrote:
> I can't remember about Puppet since I haven't used it in so long, but
> bcfg2 is basically just a giant directory structure, and we put ours in
> GIT for safekeeping and to track changes. Implementing ACLs in GIT is a
> bit of a PITA, so
On Thursday, September 06, 2012 05:06:27 PM Jeff Janes wrote:
> For updating 20 million out of 500 million rows, wouldn't a full table
> scan generally be preferable to an index scan anyway?
>
Not one table scan for each row updated ...
--
Sent via pgsql-general mailing list (pgsql-general@po
On Friday, August 31, 2012 12:41:42 PM fellipeh wrote:
> Here is error msg:
> http://postgresql.1045698.n5.nabble.com/file/n5722180/erro_PG.png
>
> sorry, but in portuguese..
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/Tigger-after-delete-with-plpgsql-tp
On Friday, August 31, 2012 12:12:32 PM fellipeh wrote:
> Yes, the error appears when I delete "nfentrada_item" row
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/Tigger-after-delete-with-plpgsql-tp
> 5722154p5722173.html Sent from the PostgreSQL - general mailing list arc
On Friday, August 31, 2012 03:14:15 PM Fellipe Henrique wrote:
> CREATE TRIGGER nfentrada_item_tr1
> BEFORE DELETE
> ON public.nfentrada_item FOR EACH ROW
> EXECUTE PROCEDURE public.nfentrada_item_ad0();
>
> here is my nfentrada_item_ad0();
>
> delete
> from MOVIMENTO
> wher
On Friday, August 31, 2012 02:10:47 PM Fellipe Henrique wrote:
> Hello, I`m try to use this code for my After Delete trigger:
>
> delete
> from MOVIMENTO
> where (IDEMPRESA = OLD.idempresa) and
> (upper(TABELA) = 'NFENTRADA_ITEM') and
> (CODIGO = OLD.idempresa_item);
>
> But
On Wednesday, August 29, 2012 12:35:32 PM Little, Douglas wrote:
> Is there a method for having unix env variables incorporated into a psql sql
> statement? Ie
> Export var='dev'
> Psql =c 'select count(*) from $var.customer;'
>
Use double-quotes, not single-quotes. Bash won't interpolate variabl
On Tuesday, August 28, 2012 11:52:26 AM Ing.Edmundo.Robles.Lopez wrote:
> Please, could you help to give peace of mind to my boss and make sure
> that the version we choose to be as smooth as possible compatible with
> version 8.3?
>
All compatibility changes are indicated in the upgrade notes fr
On Wednesday, August 22, 2012 02:43:05 PM Alan Hodgson wrote:
> The most likely way to get this done is with Slony. Setup a Slony slave,
> upgrade the slave to 9.1 with a dump/reload, run it and let Slony catch it
> up, and then promote it to be the Slony cluster master and switch your
On Wednesday, August 22, 2012 05:17:10 PM Scott Briggs wrote:
> So we have a large TB database that we need to migrate to 9.1 and I'm
> wondering if there's a way to do this process in stages.
>
> Since the date/time storage types changes between 8.3 and 8.4, I
> realize we'll have to dump the dat
On Wednesday, August 22, 2012 04:10:01 PM Andrew Hannon wrote:
> Just looking into High IO instances for a DB deployment. In order to get
> past 1TB, we are looking at RAID-0. I have heard
> (http://hackerne.ws/item?id=4266119) there might be a problem if TRIM isn't
> supported. Does anyone know if
On Friday, July 27, 2012 11:59:49 AM Ing.Edmundo.Robles.Lopez wrote:
> Hi, i have postgres 8.3 running in SCO Openserver 5.0.7
>
> today, i had problems to start psql, the error mesage was: 'FATAL
> Memory out, Detail: Failed on resqueted size ...' , and after i checked
> the process i notic
On Wednesday, July 18, 2012 12:28:00 PM Bob Pawley wrote:
> It's an insert after trigger function.
>
> The table has a column named fluid_id.
>
> Bob
Could you post the whole function? And a \d on the table?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make change
On Wednesday, July 18, 2012 11:07:34 AM Bob Pawley wrote:
> Hi
>
> I would appreciate some fresh eyes on this expression -
>
> update p_id.fluids
> set fluid_short =
> (select shape.text
> from shape, num_search
> where (select st_within(shape.wkb_geometry,
> st_geometryn(num_sea
On Wednesday, June 20, 2012 01:10:03 PM Sam Z J wrote:
> Hi all
>
> I'm curious how is wildcards at both ends implemented, e.g. LIKE '%str%'
> How efficient is it if that's the only search criteria against a large
> table? how much does indexing the column help and roughly how much more
> space is
On Wednesday, May 30, 2012 08:22:58 PM Bart Lateur wrote:
> Luckily this is a development machine, but as we don't know what causes
> the problem we fear we might one day face the exact same problem where
> it does matter: on a production machine. So we'd like to know exactly
> what went wrong..
C
On Saturday, May 19, 2012 04:42:16 PM Clemens Eisserer wrote:
> Hi again,
>
> We are still constantly getting postgresql processes killed by signal
> 9 from time to time, without any idea why or how.
> Syslog seems completly clean.
>
> In case a postgresql process would exceed some restricted res
On Saturday, March 31, 2012 01:52:37 AM clover white wrote:
> HI, i have a problem when using pg, thanks for help. :)
>
> I used command initdb, but nothing was created in my pgdata directory.
> however, I used command ps to list all the processes, and I found inidb
> process kept running all t
On Friday, March 30, 2012 10:00:31 AM Prashant Bharucha wrote:
> Hello All
>
> Could you help me to automatically convert all db request into UTF8 encode ?
>
Set your session client_encoding to match your data. That's about as close as
you can get to automatic.
http://www.postgresql.org/docs
On Tuesday, March 27, 2012 08:20:23 PM Akshay Joshi wrote:
> In my case I won't allow anyone to insert/modify the rows of sample_one
> table. I have already inserted some rows in sample_one table where I
> want one constraint is number of array elements of sample_one.param_names
> and sample.pa
On Thursday, February 16, 2012 09:18:34 PM Andrus wrote:
> PostgreSql 8.4 in windows crashes. After that Windows disk repairing was
> used to repair hard drive. After that Data/base directory from crashed
> server contains lot of files, all files are readable.
>
> PostgreSql 8.4 was reinstalled in
On Thursday, February 09, 2012 10:25:51 PM Daniel Vázquez wrote:
> Hi!
>
> I've set my PGDATA variable in profile
> export PGDATA=/home/mydata/pgsql/data
>
> Testing variable for correct set in enviroment
> $ echo $PGDATA
> /home/mydata/pgsql/data
>
> but when execute:
> $ sudo /etc/init.d/postg
On Wednesday, February 01, 2012 05:13:15 PM Christopher Opena wrote:
> Do you mean 6-12% of total iowait, or per cpu? Our average iowait in the
> last week is 34.31% of a total 1600% with an average idle of 1451.76%. Our
> iowait *does* spike occasionally (today it went up to 148.01%) but it
> do
On Wed, Feb 1, 2012 at 7:38 PM, Christopher Opena
wrote:
> > Hello folks,
> >
> > We've been running into some very strange issues of late with our
> > PostgreSQL database(s). We have an issue where a couple of queries
> > push high CPU on a few of our processors and the entire database locks
On Monday, January 23, 2012 07:54:16 PM Andrew Hannon wrote:
> It is worth noting that, the slave (seemingly) catches up eventually,
> recovering later log files with streaming replication current. Can I trust
> this state?
>
Should be able to. The master will also actually retry the logs and eve
On Tuesday, January 17, 2012 10:34:54 AM Tim Uckun wrote:
> http://www.drbd.org/ ??
> Built in hot standby and hand rolled scripts.
>
I have a few clusters running on EC2 using DRBD to replicate between
availability zones. It's not fast, but it works. If your write load is under
30MB/sec it's d
On Tuesday, January 17, 2012 10:34:54 AM Tim Uckun wrote:
> Hey Guys.
>
> It's been a while since I looked into this and it seems like new
> options have cropped up for postgres HA and scalability. Is there a
> consensus on the "best" way to achieve HA. My primary concern is HA
> but of course a
On Thursday, January 12, 2012 02:16:04 AM debian nick wrote:
> Any help will be really appreciate.
Check your pg_hba.conf file for any entries with "trust" or "ident". Remove
them and restart the server.
Also look for .pgpass files in the home directories of any user seeing this.
--
Sent via p
On Sunday, December 18, 2011 04:00:14 PM amit sehas wrote:
> Yes i was trying to determine how to make a View work in this situation.
> From reading the details on PostgreSQL Views are not persistent, ie they
> are just a SQL query short hand rather than actually creating any physical
> entity back
On Saturday, November 26, 2011 10:18:56 AM Carlos Henrique Reimer wrote:
> Hi,
>
> We're planning to move our postgreSQL database from one CPU box to another
> box.
>
> I'm considering an alternative procedure for the move as the standard one
> (pg_dump from the old, copy dump to the new box, psq
On November 16, 2011 05:07:05 PM hyelluas wrote:
> I see 900 queries sent by 1 client in 7 min with 1 click on the screen -
> does the log show the real thing?
The logs show the real thing. Gotta love ORMs.
>
>
> Is it possible to log the number of records returned by that query?
I doubt the
On November 2, 2011 08:55:39 AM Debasis Mishra wrote:
> My doubt is - Whether cluster should start the postgres service in
> secondary node during failover or postgress will be running always. My
> undersatnding was in both the node postgress will be running and pointing
> to shared dbdata. And if
On October 31, 2011 03:01:19 PM Stephen Denne wrote:
> I'm wondering whether it's worth doing anyway, simply to check that it
> doesn't do something completely unexpected, which would presumably alert
> us to something we hadn't considered.
>
Testing is always worthwhile, if only to ensure that P
On October 27, 2011 01:09:51 PM Brian Fehrle wrote:
> We've restarted the postgresql cluster, so the issue is not happening at
> this moment. but running a vmstat 10 had my 'cs' average at 3K and 'in'
> averaging around 9.5K.
Random thought, is there any chance the server is physically overheating
On October 12, 2011 03:04:30 PM Bob Hatfield wrote:
> > Anyway, a better way for you would be to do a regular backup (with
> > pg_start_backup, copy and pg_stop_backup) and then use wal
> > archive_command to keep the xlogs between 2 full backups.
>
> Thanks Julien. Can pg_start/stop_backup() be
> > rsync works fine. Why exactly can't the recovery find the backed up copy
> > of 000105390076? Please post your archive_command settings,
> > the contents of any script(s) called by that, and the recovery.conf file
> > you're using that's having problems, as well as the complete proc
On October 3, 2011 05:33:35 AM Venkat Balaji wrote:
> Did anyone observe this behavior ?? Please help !
>
> This is critical for us. I want to recommend not to use "rsync" (use cp or
> scp instead) for production backup.
>
rsync works fine. Why exactly can't the recovery find the backed up copy
On September 26, 2011 10:47:20 AM Bob Pawley wrote:
> Hi
>
> I have an error somewhere in one of the trigger functions in my database.
> The error message only told me it was a ‘Select * From (table name).
>
> Is there a global method of finding where this expression resides other
> than searchin
On September 26, 2011 05:49:50 AM Venkat Balaji wrote:
> I tried restoring the backup, after taking the full backup.
>
> Below is what i see in the "archive destination".
>
> Postgres was asking for "00010193006F" and i tried to find the
> same and below is what i find...
>
> -rw
On September 20, 2011 01:26:06 PM Hannes Erven wrote:
> So I'd like to ask if there is anything I could do by e.g. changing
> compile-time options at the slave to get things going?
>
No.
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
On September 5, 2011, MirrorX wrote:
> thx a lot for your answer.
>
> actually DRBD is the solution i am trying to avoid, since i think the
> performance is degrading a lot (i ve used it in the past). and also i
> have serious doubts if the data is corrupted in case of the master's
> failure, if
On August 29, 2011 02:34:26 PM you wrote:
> On Mon, Aug 29, 2011 at 3:46 PM, Alan Hodgson wrote:
> > On August 29, 2011 01:36:07 PM Lonni J Friedman wrote:
> >> I have several Linux-x68_64 based dedicated PostgreSQL servers where
> >> I'm experiencing signifi
On August 29, 2011 01:36:07 PM Lonni J Friedman wrote:
> I have several Linux-x68_64 based dedicated PostgreSQL servers where
> I'm experiencing significant swap usage growth over time.
It's the Linux kernel that does it, not PostgreSQL. Set vm.swappiness=0
(usually in /etc/sysctl.conf) and put t
On August 24, 2011 08:33:17 AM Samba wrote:
> One strange thing I noticed is that the pg_xlogs on the master have
> outsized the actual data stored in the database by at least 3-4 times,
> which was quite surprising. I'm not sure if 'restore_command' has anything
> to do with it. I did not understa
On August 19, 2011 07:01:33 AM Gauthier, Dave wrote:
> Is there a way to get the linux idsid of a user, even for a remote network
> connection?
>
> I could write a pg-perlu to get this, but I suspect it won't give me the
> original user when there's a remote connect.
>
> Thanks for any suggestion
On July 7, 2011 12:30:35 PM Rich Shepard wrote:
> On Thu, 7 Jul 2011, Alan Hodgson wrote:
> > It implies the composite is unique. Not sta_type.
>
>OK. Now I understand. How, then, do I add a unique constraint to each
> component of the composite key so I can add them as f
On July 7, 2011 11:55:25 AM Rich Shepard wrote:
> On Thu, 7 Jul 2011, Alan Hodgson wrote:
> > You need a unique index on station_type.sta_type
>
> Alan,
>
>station_type(sta_type) is part of a composite primary key. Doesn't
> primary key automatically imply uni
On July 7, 2011 10:40:11 AM Rich Shepard wrote:
> alter table station_information add column sta_type varchar(50)
> unique not null references station_type(sta_type);
> NOTICE: ALTER TABLE / ADD UNIQUE will create implicit index
> "station_information_sta_type_key" for table "station_information"
On June 15, 2011 01:18:27 PM BRUSSER Michael wrote:
> Unless there's no other options I don't want to use sed or break file into
> pieces, if possible,
iconv loads everything into RAM. You can use "split", convert the pieces, and
then recombine, I did that when converting a large database to utf-
On June 9, 2011 05:15:26 AM Håvard Wahl Kongsgård wrote:
> Hi, I have performance issues on very large database(100GB). Reading from
> the database is no problem, but writing(or heavy writing) is a nightmare.
> I have tried tuning postgresql, but that does not seem to improving the
> writing perfor
On June 7, 2011 04:38:16 PM owen marinas wrote:
> Thx, Merci, Gracias Rodrigo
> it worked indeed, Im wondering why replication is not included in "All"
>
Probably because it gives access to all the data being written to the
database.
--
Obama has now fired more cruise missiles than all other N
On May 6, 2011, Iain Barnett wrote:
> Would anyone be able to point out to me how I can get the template1
> database to be utf8 and en_GB? (or US, I'm not *that* fussed)
Use the --encoding and --locale options to initdb.
On April 14, 2011 08:10:47 am Dan Biagini wrote:
> I suspect that it may have occurred during a filesystem level backup
> (ie pg_start_backup(), tar -czf..., pg_stop_backup()), as I performed
> a backup and moved the database to a different system. After
> restoring the files and starting postgre
On February 2, 2011, "William Bruton" wrote:
> How do I know which version to upgrade to from 8.1.4?
>
Well, 8.1 is no longer supported, it seems. So an upgrade to any supported
version will likely require application changes, or at least thorough
testing. You might as well go right to 9.0.3 t
On January 14, 2011, "Jaiswal Dhaval Sudhirkumar"
wrote:
> Hi,
>
> I am looking for active-active clustering solution.
>
> I have one SAN box and two separate NODES, where I need to create
> active-active cluster. My data directory would be one and mounted to the
> SAN box for both the nodes. (
On January 7, 2011, gvim wrote:
> PostgreSQL 9.0.1/pgAdminIII 1.12.1
>
> I want to copy selected tables from one database to another and maintain
> the sequences which I originally setup with:
>
> CREATE SEQUENCE venues_id_seq START WITH 1122;
> ALTER TABLE venues ALTER COLUMN id SET DEFAULT nex
On December 28, 2010, "Bob Pawley" wrote:
> It's often a good idea to maintain function definitions outside the
> database,
> under version control, and apply them to the database from there.
>
> I would appreciate a more detailed explanation of this.
Treat them like source code.
>
> Bob
>
>
On December 28, 2010, Adrian Klaver wrote:
> On 12/28/2010 07:40 PM, Bob Pawley wrote:
> >> Open the file in Wordpad and see if it looks better.
> >>
> >> I downloaded an sql editor and it looks the same in it as well.
> >>
> >> At least the editor will make it easier to fix the problem. However
On October 29, 2010, "Dean Gibson (DB Administrator)"
wrote:
> On 2010-10-29 11:17, Alan Hodgson wrote:
> > I'm curious about this too. It seems that currently I'd have to
> > rebuild any additional slaves basically from scratch to use the new
> > mas
On October 29, 2010, "Dean Gibson (DB Administrator)"
wrote:
> My question is, how do I configure the other three (still) hot_standby
> boxes to now use the new primary? Clearly I can change the
> "recovery.conf" file on each standby box, but that seems like an
> unnecessary nuisance.
I'm curio
On October 26, 2010 10:18:41 am Ozz Nixon wrote:
> I have hung off indexes for each column, to resolve my previous
> "performance" issue from 3+ weeks ago. However, COUNT() is still dog slow
> - this table is a write once, read many... *never* update, nor delete.
>
> Any suggestions?
If you need
On September 23, 2010 01:49:50 pm kongs...@stud.ntnu.no wrote:
> Hi,
> I have a copy of "/usr/local/pgsql/data" from old server. Is it
> possible to do a dump of the sql databases in this directory, so that
> I can easily migrate them to my current system?
>
You should be able to launch a postmas
1 - 100 of 261 matches
Mail list logo
