Hi, does anyone know if there's a compression function to let me store
in gzipped/deflate format TEXT or Bytea fields.
Please correct me if I'm wrong, but I also wonder if this function is
really needed since I've read large objects are stored with TOAST, hence
compression is already there.
Leonardo M. Ramé wrote:
> Hi, does anyone know if there's a compression function to let me store
> in gzipped/deflate format TEXT or Bytea fields.
>
> Please correct me if I'm wrong, but I also wonder if this function is
> really needed since I've read large objects are stored with TOAST, hence
>
Hi everyone,
Questions about pg_xlogs again...
I have two Postgresql 9.1 servers in a master/slave stream replication
(hot_standby).
Psql01 (master) is backuped with Barman and pg_xlogs is correctly
purged (archive_command is used).
Hower, Psql02 (slave) has a huge pg_xlog (951 files, 15G for 7
Le 16 juin 2015 10:57 AM, "Xavier 12" a écrit :
>
> Hi everyone,
>
> Questions about pg_xlogs again...
> I have two Postgresql 9.1 servers in a master/slave stream replication
> (hot_standby).
>
> Psql01 (master) is backuped with Barman and pg_xlogs is correctly
> purged (archive_command is used).
Hi Craig,
Thanks for your response.
Le 16/06/2015 03:58, Craig Ringer a écrit :
On 15 June 2015 at 17:19, Sylvain MARECHAL wrote:
Is it possible to completely detach a node so that it can live alone
Yes. On a different node to the one you want to remove,
bdr.bdr_part_by_node_names(ARRAY['the
On 16 June 2015 at 18:40, Sylvain MARECHAL wrote:
> Nothing special in the logs here. What I would like to emphasize is that a
> single node can not live alone.
Yes, that's right.
"Single node BDR", i.e. running with BDR enabled but no peers, would
be nice to support for testing and robustness
On Tue, 16 Jun 2015 04:45:52 -0300
"Leonardo M. Ramé" wrote:
> Hi, does anyone know if there's a compression function to let me store
> in gzipped/deflate format TEXT or Bytea fields.
>
> Please correct me if I'm wrong, but I also wonder if this function is
> really needed since I've read larg
Many thanks to all, I resolved my issue. A rules has lacked in iptables, like
this:
iptables -A INPUT -p tcp --dport 5997 -j ACCEPT
Bye.
Meph
--
View this message in context:
http://postgresql.nabble.com/PostgreSQL-and-iptables-tp5853587p5854028.html
Sent from the PostgreSQL - general maili
Michael, thanks for checking,
I tried it again today and it is now working so I must have forgotten something.
John
> Date: Tue, 16 Jun 2015 08:33:09 +0900
> Subject: Re: [GENERAL] RegisterBackgroundWorker does not actually start a bg
> worker process in
I have these 2 tables:
CREATE TABLE "stuff" ("number" integer NOT NULL PRIMARY KEY, "title"
varchar(40) NOT NULL);
CREATE TABLE "stuff_ext" ("stuff_ptr_id" integer NOT NULL PRIMARY KEY,
"extra" integer NOT NULL);
ALTER TABLE "stuff_ext" ADD CONSTRAINT
"stuff_ext_stuff_ptr_id_5a4ee8edae53404b"
I don't think so. There is no archive_command and the master doesn't
ship its wal here.
But how can I check that ?
2015-06-16 12:41 GMT+02:00 Guillaume Lelarge :
> Le 16 juin 2015 10:57 AM, "Xavier 12" a écrit :
>>
>> Hi everyone,
>>
>> Questions about pg_xlogs again...
>> I have two Postgresql 9
Using pg_upgrade in 9.4 CentOS release 6.6 (Final) (from PostgreSQL 9.1.15)
it fails when GRANTING permits to roles.
Checking pg_upgrade_dump_globals.sql, I see the point of failure is caused
by the -- Role memberships section.
In there I see the following troublesome lines.
-- Role memberships
Melvin Davidson writes:
> Using pg_upgrade in 9.4 CentOS release 6.6 (Final) (from PostgreSQL 9.1.15)
> it fails when GRANTING permits to roles.
>
> Checking pg_upgrade_dump_globals.sql, I see the point of failure is caused by
> the -- Role memberships section.
>
> In there I see the following
Yup, that looks like the problem.
Doing:
postgres=# SELECT * FROM pg_auth_members
postgres-# WHERE roleid NOT IN (SELECT oid FROM pg_authid);
Yields, 11 Rows, so for sure someone must have been messing around. Thanks.
On Tue, Jun 16, 2015 at 11:58 AM, Jerry Sievers
wrote:
> Melvin Davidson wr
Alvaro Herrera wrote:
> I see another hole in this area. See do_start_worker() -- there we only
> consider the offsets limit to determine a database to be in
> almost-wrapped-around state (causing emergency attention). If the
> database in members trouble has no pgstat entry, it might get comple
Thomas Munro wrote:
> Thanks. As mentioned elsewhere in the thread, I discovered that the
> same problem exists for page boundaries, with a different error
> message. I've tried the attached repro scripts on 9.3.0, 9.3.5, 9.4.1
> and master with the same results:
>
> FATAL: could not access s
2015-06-16 15:55 GMT+02:00 Xavier 12 :
> I don't think so. There is no archive_command and the master doesn't
> ship its wal here.
> But how can I check that ?
>
>
What's the complete path to the directory on the salve that contains 951
files? what does PostgreSQL say on its log files?
2015-06-16
On Wed, Jun 17, 2015 at 6:58 AM, Alvaro Herrera
wrote:
> Thomas Munro wrote:
>
>> Thanks. As mentioned elsewhere in the thread, I discovered that the
>> same problem exists for page boundaries, with a different error
>> message. I've tried the attached repro scripts on 9.3.0, 9.3.5, 9.4.1
>> an
Just started playing with BDR. Originally setup the environment on two
separate servers as per the quick start guid and used the sql commands to
add nodes. Moving on to command line, I am running into some issues.
I am sure I am just overlooking something really simple. But, on the
primary node I
On Tue, Jun 16, 2015 at 6:55 PM, Xavier 12 wrote:
> Hi everyone,
>
> Questions about pg_xlogs again...
> I have two Postgresql 9.1 servers in a master/slave stream replication
> (hot_standby).
>
> Psql01 (master) is backuped with Barman and pg_xlogs is correctly
> purged (archive_command is used)
Hi all,
Looking for confirmation there is an issue with pg_dump failing after upgrade
to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux.
-bash-4.1$ pg_dump -V
pg_dump (PostgreSQL) 8.4.9
-bash-4.1$ pg_dump -h localhost -C Hogwarts -a -t mafs -f zz
pg_dump: Dumping the contents of table "mafs"
On Tue, 16 Jun 2015 16:55 Xavier 12 wrote:
Hi everyone,
Questions about pg_xlogs again...
I have two Postgresql 9.1 servers in a master/slave stream replication
(hot_standby).
Psql01 (master) is backuped with Barman and pg_xlogs is correctly
purged (archive_command is used).
Hower, Psql02 (sl
On Tue, 16 Jun 2015 13:33:12 +0001
Filipe Pina wrote:
> I have these 2 tables:
>
> CREATE TABLE "stuff" ("number" integer NOT NULL PRIMARY KEY, "title"
> varchar(40) NOT NULL);
> CREATE TABLE "stuff_ext" ("stuff_ptr_id" integer NOT NULL PRIMARY KEY,
> "extra" integer NOT NULL);
> ALTER TABLE "
Hi all;
We are running a multi-TB bioinformatics system on PostgreSQL and use a
denormalized schema in
places with a lot of tsvectors aggregated together for centralized
searching. This is
very important to the performance of the system. These aggregate many
documents (sometimes tens of thou
24 matches
Mail list logo
