Re: [ADMIN] Pg 9.1 master-slave replication
> > Hello, > > Could explain somebody what will happen, if the slave server fails ? > Will it affect the master functionality/availability ? nothing!!! the Master continuo work. ;-))) > I'm using simple master-slave replication with 2 servers. > > > -- > Best regards > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin--- > This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE > running at host imx2.etecsa.cu > Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> > Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] top posting?
> Just out of curiousity, I see comments like this all the time: > >> (*please* stop top-posting). > > I've been participating in newsgroups since UUCP days, and I've never > encountered a group before that encouraged bottom posting. Bottom posting > has traditionally been considered rude -- it forces readers to scroll, > often through pages and pages of text, to see a few lines of original > material. > > The most efficient strategy, one that respects other members' time, is to > briefly summarize your point at the TOP of a posting, then to *briefly* > quote only the relevant parts of the post to which you are replying, and > bottom-post after the quoted text. That lets your reader quickly see if > it's relevant or not, and move on to the next post. > > Contributors in these newsgroups seem to think it's OK to quote five pages > of someone else's response, then add one or two sentences at the bottom > ... > it's just laziness that forces readers to wade through the same stuff over > and over in each thread. > > How did the Postgres newsgroups get started with this "only bottom post" > idea? > > (I'm not trying to start a flame war, just genuinely curious.) > Prefer a brief note of what this issue, to follow in him. And not I have to go elsewhere to find out whether or not interest me the news, avoid to nuisance. Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Migration of server
> Hi everybody, this is my first message in this list. The company where i > work is bringing maintenance service of PostgreSQL to another company, and > currently they have installed PostgreSQL 9.1.1, and they want to move to > 9.3 version when it will come out. So, because the difference of versions, > and because it was installed by compiling it (using source code), and > because the 9.1.1 installation is in a different directory than the > default, they decided to replace 9.1.1 version with 9.3 (no upgrade, but > replace it). > > Currently, they only have one database in production of 2.2 GB with some > procedures and triggers. So, my plan to execute this database installation > is the next: > > >1. Install PostgreSQL 9.3 from postgresql repository > (yum.postgresql.org) >with a different port to avoid interrupt the production PostgreSQL > instance >operation >2. Tune the database parameters in postgresql.conf, also create the > same >rules in pg_hba as the production instance, configure log and so on. >3. At the end of the operations day, create a backup of the production >database and then restore it into the new instance >4. Test the new instance with the PHP applications that use it and >verify that all is in order >5. Stop the old instance and change the port to another port, then >change the port of the new instance to 5432 in order to avoid change > the >network configuration, permissions and so on. > > But really is the first time that i do that, so i don't know if i'm > missing > something or there's something wrong about i'm planning to do, so i will > appreciate very much if you can guide me about what steps i have to do > exactly and considerations during this process. Not, only bad thing is that the 9.3 is still in beta version. Use 9.2. Write list in spanish Too ;-) Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Creating new cluster by copying directory?
> All: it would take ~4 hours to pg_restore a backup. I want to quickly > create a duplicate cluster (for testing). My idea: > > 1. pg_ctlcreatecluster 9.1 test > 2. rm /var/lib/postgresql/9.1/test/* > 2. cp /var/lib/postgresql/9.1/main /var/lib/postgresql/9.1/test > 3. pg_ctlcluster 9.1 test start > > Is this viable? If not, is there another way to create a duplicate cluster > in a timely fashion? Test Repmgr works with the same philosophy. ;-) Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Creating new cluster by copying directory?
> So it's safe to copy the files in /var/lib/postgresql/9.1/main to > /var/lib/postgresql/9.1/test while main is running? > Yes, but the server where copy is stop. Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] restoring a table after an online backup
> Hello, > > I was just wondering: Is it possible to restore a specific table from an > online backup? > Or is it only possible if we first restore the backup, replay all the > logs, > and then take the table files? > It depends on how you do the copy. To do comados with SQL, you can find to with the sql of the table you want. Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Help with PITR in PostgreSQL 8.4
> Hi Chiru, I have done archiving on primary server, and recovery on > standby server, howerver, after the first recovery I am unable to > recover more wal files on standby server > > Can it be possible in 8.4 ? or just in 9.1 ? > > This is the recovery I use: > > << EOF > > restore_command = '/usr/lib/postgresql/8.4/bin/pg_standby -l -d -s 2 -t > /var/run/postgresql/8.4-main.trigger > /var/lib/postgresql/8.4/main/wal-archive %f %p %r > 2>>/var/log/postgresql/postgresql-8.4-main-standby.log' > recovery_end_command = 'rm -f /var/run/postgresql/8.4-main.trigger' > > EOF > > Hello Nestor I use its: standby_mode = 'on' primary_conninfo = 'host=X.X.X.X port=5432 user= password=YTT' trigger_file = '/var/pgsql/data/pg_failover_trigger' restore_command = 'cp /wal/%f /var/lib/postgresql/8.4/main/"%p"' Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Help with PITR in PostgreSQL 8.4
> >> Hello Nestor >> >> I use its: >> >> standby_mode = 'on' >> primary_conninfo = 'host=X.X.X.X port=5432 user= password=YTT' >> trigger_file = '/var/pgsql/data/pg_failover_trigger' >> restore_command = 'cp /wal/%f /var/lib/postgresql/8.4/main/"%p"' > Ok, but those instructions are for 9.1 not for 8.4, I would like to be > sure if there is any way to perform countinus archiving then recovery > then backup and loop over this every day whithout having to rsync every > time I recover the standby database (8.4) > See you: http://www.postgresql.org.es/node/238 http://www.postgresql.org/docs/8.3/interactive/continuous-archiving.html Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] PGPOOL II No funciona agrupamiento de conecciones
> Buenas tardes compañeros, tego problemas con un pgpool version 3.0.4.1 > en > ubuntu, > > tengo configurado un backend y el parametro connection_cache = true > > Se configuro una app web para que se conecte a dicho pool se conecta bien > pero no reutiliza las coneccciones es decir cuando me conecto con el > pgadmin al gestor, no al pool, se muestran varias conecciones con el mismo > usuario a la misma db, gracicas de antemano por cualquier comentario al > respecto de dicho comportamiento, tengo entendido que deberia reutilizar > dicha coneccion. ¿Qué te hace pensar que no esta reutilizando tus conexiones? Saludos, Gilberto Castillo La Habana, Cuba --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] postgres database user account
El mié, 30-06-2010 a las 16:15 -0400, Maria L. Wilson escribió: > that sounds similar to what we are trying to accomplish. Looks like > what we need to do is use the sudo at the OS level - and remove the > postgres db user account altogether giving specific users the privs > (or create roles) that accomplish what they need. > or only allow IP connections and remove the sock LOCAL and remove ALL of pg_hba Usuaris -- Redards, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Haban.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
El mié, 09-03-2011 a las 13:58 +0100, Dyonisius Visser escribió: > hi guys > > I am in the process of converting my network to IPv6 only (well, as > much as possible). > Since our own network has fully functional IPv6 connectivity, I should > be able to move all services that are used internally only, to IPv6 > only. > Postgres is one of those services. > > I could not find anywhere in the docs how to configure this. > However, the following seems to do the trick: > > listen_addresses = '::' > > This will make postgres listen on IPv6 only: > > root@cajones:~# telnet 127.0.0.1 5432 > Trying 127.0.0.1... > telnet: Unable to connect to remote host: Connection refused > > root@cajones:~# telnet ::1 5432 > Trying ::1... > Connected to ::1. > Escape character is '^]'. > > Might be an idea to add this to the docs. Maybe!!. -- Regards, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
> > Maybe!!. > > Interesting. How would someone listen only on IPv4 addresses? In documentation there are few examples of its use, there are several networks that only use IPv6 -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx2.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
> My big question is whether '::' is supported on all platforms that > support IPv6, and whether there is an IPv4-only syntax. Umm, you have to try, at least there is not much documented about it. -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
> OK, let's skip documenting this then. They can already do this via > pg_hba.conf. What would the postgresal.conf listen_addresses? -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
El jue, 10-03-2011 a las 21:11 +0100, Dyonisius Visser escribió: > On 10 March 2011 19:37, Bruce Momjian wrote: > > > Interesting. How would someone listen only on IPv4 addresses? > > listen_addresses = '0.0.0.0' > > root@toad:/etc/postgresql/8.4/main# telnet ::1 5432 > Trying ::1... > telnet: Unable to connect to remote host: Connection refused > > root@toad:/etc/postgresql/8.4/main# telnet 127.0.0.1 5432 > Trying 127.0.0.1... > Connected to 127.0.0.1. > Escape character is '^]'. > OK, -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx2.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
El jue, 10-03-2011 a las 15:33 -0500, Bruce Momjian escribió: > Dyonisius Visser wrote: > > On 10 March 2011 21:03, Bruce Momjian wrote: > > > > > OK, let's skip documenting this then. ?They can already do this via > > > pg_hba.conf. > > > > Restricting access via pg_hba.conf is something else than listening > > (or not) on sockets... > > > > FYI, the listen_addresses is basically the same as sshd's ListenAddress. > > Yes, listen_addresses prevents anyone from even binding to the address. I keep thinking you should put that information somewhere accessible comun. -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx2.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] Listen on IPv6 only
> > > > Restricting access via pg_hba.conf is something else than listening > > > > (or not) on sockets... > > > > > > > > FYI, the listen_addresses is basically the same as sshd's ListenAddress. > > > > > > Yes, listen_addresses prevents anyone from even binding to the address. > > > > I keep thinking you should put that information somewhere accessible > > comun. > > I can add it to the documentation now that we have more reports. Thank you!! -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx2.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
Re: [ADMIN] constraint triggers
El mié, 28-09-2011 a las 08:54 -0400, Maria L. Wilson escribió: > Hi all > > I would like to start a dialogue and hear general feedback about the > use of constraint triggers in postgres (8.4.5). > > Our overall issue is that using general triggers is causing slow > inserts (from locking issues) in our database. Here are some details: > > A little background (jboss/j2ee/hibernate/linux). > We have 3 basic triggers on a particular database table - one for > inserts, one for updates & another for deletes and they keep track of > a "granule count" that is used in reporting. This field (gracount) is > stored in another table called dataset. An example of the insert > trigger/function is as follows: > > -- > CREATE TRIGGER increment_dataset_granule_count > AFTER INSERT > ON inventory > FOR EACH ROW > EXECUTE PROCEDURE increment_dataset_granule_count(); > > CREATE OR REPLACE FUNCTION increment_dataset_granule_count() > RETURNS trigger AS > $BODY$ > DECLARE > BEGIN > IF NEW.visible_id != 5 THEN > UPDATE dataset > SET gracount = gracount + 1 > WHERE dataset.inv_id = NEW.inv_id; >END IF; > RETURN NULL; > END; > $BODY$ > LANGUAGE plpgsql VOLATILE > COST 100; > ALTER FUNCTION increment_dataset_granule_count() OWNER TO jboss; > --- Replace RETURN NULL for RETURN NEW -- Saludos, Gilberto Castillo Edificio Beijing. Miramar Trade Center. Etecsa. Miramar, La Habana.Cuba. --- This message was processed by Kaspersky Mail Gateway 5.6.28/RELEASE running at host imx3.etecsa.cu Visit our web-site: <http://www.kaspersky.com>, <http://www.viruslist.com> -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
