Long, Jie | 24 Jun 22:30 2016

Re: [BUGS] BUG #14210: DB crash: system logger process was terminated by exception 0xFFFFFFFFwith exception 0xFFFFFFFF

Add update: We have tried to create crashdumps under data directory. Nothing was generated.  This leave us
not much option for debugging the issue. 

Thanks,

Jie 

--

-- 
Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Andreas Joseph Krogh | 24 Jun 13:36 2016

Updated RUM?

Hi.
 
<at> PostgresPro; Will there be any updates to the rum git-repo any time soon?
 
I understand you're working hard on this, care to share some vision/roadmap? I'm specifically interested in if RUM will support the same datatypes as GIN supports (arrays, JSON etc.), and what opclasses you plan to implement (for equalty and sorting). Will there be some kind of btree_rum like there is for btree_gin, to add RUM-support for the types there exists Btree-support for?
 
Thanks.
 
--
Andreas Joseph Krogh
CTO / Partner - Visena AS
Mobile: +47 909 56 963
Thomas Kellerer | 24 Jun 07:44 2016
Picon
Picon

9.6 beta2 win-x64 download links still point to beta1

Hello,

the Beta2 downloads on 

  http://www.enterprisedb.com/products-services-training/pgdownload
  http://www.enterprisedb.com/products-services-training/pgbindownload

still lead to Beta1 for the Windows 64bit builds. 

All others properly link to beta1

Thomas

--

-- 
Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Justin Dearing | 24 Jun 04:19 2016
Picon
Gravatar

Concerned to discover DOMAINs can be the same as built in types with no escaping

Hello,

We happen to have in our schema the following domain.

CREATE DOMAIN public.name varchar(50) NOT NULL;

This was done before me. We assumed this was used in many tables in our app. Then I wrote a function with a return clause like the following:

RETURNS (
id INT,
name name,
other_names name ARRAY
)

This worked fine until CI tried to build this on a postgres 9.3 box (we are mostly 9.1, but are fixing that). Then it failed.

So then I discovered that there is a built in type called pg_catalog.name as well as my public.name. Followed by the discovery that you can't have arrays of domains. This query showed two rows

SELECT typnamespace, typname 
FROM pg_catalog.pg_type typ
WHERE typname = 'name';

Then there was wailing and gnashing of teeth, and I made everything explicitly varchar, and everything was all good, except I have to fix unit tests. Oh and nothing is actually using our domain, as demonstrated by this query:

SELECT attrelid::regclass AS table_name,
attname, atttypid::REGTYPE
FROM pg_catalog.pg_attribute
WHERE atttypid::REGTYPE IN ('name', 'public.name')
ORDER BY atttypid DESC, attrelid::regclass

Based on this, and some consultations with friends who know more about postgres than I, I'd like to propose that domains not be allowed to be the same name as built in types or at the very least give a warning. The fact that I have to quote keywords, but not even need to quote built in types is bothersome. Here are examples of queries and behaviors I expect


CREATE DOMAIN "INTO" char(5); -- Does work. Should work without a warning. The error you get for doing it unquoted is sufficient IMHO
CREATE DOMAIN int CHAR(50); -- Does work. Id prefer it not to work. Alternatively it could work but emit a warning.
CREATE DOMAIN public.int CHAR(50); -- Does work. I could see the argument for it working, but would prefer it didn't work. Should still emit a warning its overriding a base 

Since I'm returning to postgres after close to a decade, I figured I'd ask here for feedback before posting to the hackers list.

Regards,

Justin Dearing
Dusan Milanov | 23 Jun 18:13 2016
Picon

Transaction serialization

Hi,

A question about transactions: does postgres report serialization errors before a transaction is committed? Obviously, it does on commit, but how about previous statements? Can there be an ERRCODE_T_R_SERIALIZATION_FAILURE error as a response to anything else but the commit?

Best regards,

Dusan Milanov
Jason Dusek | 23 Jun 08:46 2016
Picon
Gravatar

client_min_messages and INFO

Hi List,

I notice that INFO is not included in the list of settable levels for client_min_messages:


This seems to be true several versions back so I wonder: what is the rationale? Is it like the reverse of LOG?

Kind Regards,
  Jason Dusek
sudalai | 23 Jun 08:38 2016
Picon

ERROR: missing chunk number 0 for toast value while using logical decoder.\


I am using PostgresSQL 9.5.0. 
I have customized :
https://github.com/michaelpq/pg_plugins/tree/master/decoder_raw to get
result as json. It works fine. suddenly i getting below exception while
consuming or peeking changes through that logical slot. 
Does postgres removed the  rows needed for that slot??
Kindly help me to find the problem.

db=# select * from pg_logical_slot_get_changes('lslot',NULL,1);
ERROR:  missing chunk number 0 for toast value 857563 in pg_toast_782254
CONTEXT:  slot "lslot", output plugin "rep_slot", in the change callback,
associated LSN 2E/3C26D6F0

 select * from pg_class where relname like 'pg_toast_782254';
-[ RECORD 1 ]-------+----------------
relname             | pg_toast_782254
relnamespace        | 99
reltype             | 782273
reloftype           | 0
relowner            | 10
relam               | 0
relfilenode         | 782272
reltablespace       | 0
relpages            | 464
reltuples           | 2066
relallvisible       | 464
reltoastrelid       | 0
relhasindex         | t
relisshared         | f
relpersistence      | p
relkind             | t
relnatts            | 3
relchecks           | 0
relhasoids          | f
relhaspkey          | t
relhasrules         | f
relhastriggers      | f
relhassubclass      | f
relrowsecurity      | f
relforcerowsecurity | f
relispopulated      | t
relreplident        | n
relfrozenxid        | 1982173
relminmxid          | 1
relacl              | 
reloptions          | 

Thanks In Advance.

-----
sudalai
--
View this message in context: http://postgresql.nabble.com/ERROR-missing-chunk-number-0-for-toast-value-while-using-logical-decoder-tp5909194.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

--

-- 
Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Michelle Schwan | 22 Jun 20:36 2016
Picon

Postgres 9.5.2 upgrade to 9.6

I have a question about the upgrade from 9.5.2 to 9.6

 

I know 9.6 is still in beta – but I’m trying to be ahead of the game!

 

I found instructions on how to move from 9.4 to 9.5.  I will try testing these steps with 9.5 to 9.6

 

However, I was wondering if there is a “nicer” way to upgrade – similar to the GUI installation.  I want to be able to have a “nice” recommendation for our clients when we request that they upgrade!  I would like this for the Major1 and Major2 updates.

 

Is this possible or even available now?

 

Thanks,

Michelle Schwan

Database Developer  |  Architecture

mschwan <at> opentext.com

Phone: (519) 888 7111 ext 3241

Website:

www.opentext.com

 



This email message is confidential, may be privileged, and is intended for the exclusive use of the addressee. Any other person is strictly prohibited from disclosing or reproducing it. If the addressee cannot be reached or is unknown to you, please inform the sender by return email and delete this email message and all copies immediately.

 

Ramalingam, Sankarakumar | 21 Jun 21:34 2016

Help on recovering my standby

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 standby and primary once in a while they are in sync?

 

Currently I am working on a CERT server and hence there is no outage concerns. I need to repeat the same process on prod once I get it going successfully. Any help is appreciated.

 

 

Thanks

Kumar Ramalingam

Global Database Administration

Elavon, Atlanta , GA

 

678 731 5288

 

The information contained in this e-mail and in any attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. This message has been scanned for known computer viruses.

SDAG | 22 Jun 13:00 2016
Picon

pg_restore error-s after pg_dump

Hi
Postgres version : 
*PostgreSQL 9.2.4 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7
20120313 (Red Hat 4.4.7-3), 64-bit*

We transfer from one server to another (with better cpu an ram) our system
using vm converter and when I try to backup database have an error :

*pg_dump: reading schemas
pg_dump: reading user-defined tables
pg_dump: reading extensions
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined operator families
pg_dump: reading user-defined text search parsers
pg_dump: reading user-defined text search templates
pg_dump: reading user-defined text search dictionaries
pg_dump: reading user-defined text search configurations
pg_dump: reading user-defined foreign-data wrappers
pg_dump: reading user-defined foreign servers
pg_dump: reading default privileges
pg_dump: reading user-defined collations
pg_dump: reading user-defined conversions
pg_dump: reading type casts
pg_dump: reading table inheritance information
pg_dump: reading rewrite rules
pg_dump: finding extension members
pg_dump: finding inheritance relationships
pg_dump: reading column info for interesting tables
pg_dump: finding the columns and types of table "account_account"
pg_dump: [archiver (db)] query failed: ERROR:  missing chunk number 0 for
toast value 3297740 in pg_toast_2619
pg_dump: [archiver (db)] query was: SELECT a.attnum, a.attname, a.atttypmod,
a.attstattarget, a.attstorage, t.typstorage, a.attnotnull, a.atthasdef,
a.attisdropped, a.attlen, a.attalign, a.attislocal,
pg_catalog.format_type(t.oid,a.atttypmod) AS atttypname,
array_to_string(a.attoptions, ', ') AS attoptions, CASE WHEN a.attcollation
<> t.typcollation THEN a.attcollation ELSE 0 END AS attcollation,
pg_catalog.array_to_string(ARRAY(SELECT pg_catalog.quote_ident(option_name)
|| ' ' || pg_catalog.quote_literal(option_value) FROM
pg_catalog.pg_options_to_table(attfdwoptions) ORDER BY option_name), E',
    ') AS attfdwoptions FROM pg_catalog.pg_attribute a LEFT JOIN
pg_catalog.pg_type t ON a.atttypid = t.oid WHERE a.attrelid =
'274619'::pg_catalog.oid AND a.attnum > 0::pg_catalog.int2 ORDER BY
a.attrelid, a.attnum*

I solve it using *reindexdb *,after I try* pg_dump -U postgres my_db >
/home/mydb.backup* and it was successfull. Then I try to restore database to
ensure that backup is valid 
*psql -U postgres new_db < /home/mydb.backup*

And have an errors :

*ERROR : extra data after last expected column
Context: COPY tbl1, line1: "1 2013-12-02 2013-12-02  9387.74 
9775.46211485490864940000"   6180.9500000000   80262 ...."
ERROR : column "id" of relation "tbl1" does not exists
invalid command \N
invalid command \N
invalid command \N
..... 
invalid command \N
invalid command \.
ERROR:  syntax error at or near "87685"
LINE 1: 87685 SO87690 1 170468 2015-05-30 2015 05 30 
        ^
invalid command \.

ERROR:  duplicate key value violates unique constraint "ir_act_client_pkey"
DETAIL:  Key (id)=(103) already exists.
CONTEXT:  COPY ir_act_client, line 21: ""
ERROR:  duplicate key value violates unique constraint
"ir_act_report_xml_pkey"
DETAIL:  Key (id)=(733) already exists.
CONTEXT:  COPY ir_act_report_xml, line 59: ""
ERROR:  duplicate key value violates unique constraint "ir_act_server_pkey"
DETAIL:  Key (id)=(703) already exists.
CONTEXT:  COPY ir_act_server, line 6: ""
ERROR:  duplicate key value violates unique constraint "ir_act_window_pkey"
DETAIL:  Key (id)=(1) already exists.
CONTEXT:  COPY ir_act_window, line 235: "334    Last Product Inventories       
ir.actions.act_window   \N      1       2013-07-03 10:39:48.399509 
2013-12-16 16:38:..."
ERROR:  duplicate key value violates unique constraint
"ir_act_window_group_rel_act_id_gid_key"
DETAIL:  Key (act_id, gid)=(76, 1) already exists.
CONTEXT:  COPY ir_act_window_group_rel, line 14: ""
ERROR:  duplicate key value violates unique constraint
"ir_act_window_view_pkey"
DETAIL:  Key (id)=(100) already exists.
CONTEXT:  COPY ir_act_window_view, line 88: ""*

Any advice to solve this problem ?

--
View this message in context: http://postgresql.nabble.com/pg-restore-error-s-after-pg-dump-tp5909084.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

--

-- 
Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Vlad Arkhipov | 22 Jun 11:10 2016
Picon
Gravatar

Protect a table against concurrent data changes while allowing to vacuum it

Hello,

I have a constraint that requires a table to be locked before checking 
it (i.e. no more than 2 records with the same value in the same column). 
If I lock the table in the SHARE ROW EXCLUSIVE mode, any vacuuming (or 
autovacuuming) process prevents me from checking the constraint. What 
are possible solutions?

--

-- 
Sent via pgsql-general mailing list (pgsql-general <at> postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


Gmane