Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
row is too big: size 8168, maximum size 8160 - Mailing list pgsql-admin
From
Mario De Frutos Dieguez
Subject
row is too big: size 8168, maximum size 8160
Date
July 11, 2018
20:16:43
Msg-id
CAFYwGJ0Sphm9m3noXMgYf=1iDCn1=V2+7+VCD-nRg+C21Ee-gA@mail.gmail.com
Whole thread
Raw
Responses
Re: row is too big: size 8168, maximum size 8160
(Tom Lane <tgl@sss.pgh.pa.us>)
Re: row is too big: size 8168, maximum size 8160
(ramsiddu007 <ramsiddu007@gmail.com>)
List
pgsql-admin
Tree view
Hello every one!
I've found this error message and it's driving me crazy.
I have a table with 790 numeric columns, I'm trying to make an INSERT INTO x SELECT... and in the same column/s I'm getting this message.
I've tried everything VACUUM FULL, Batch the insert with updates...but nothing always the same error.
THe BLCKSZ is set to 8Kb here:
https://github.com/postgres/postgres/blob/master/src/include/pg_config.h.in#L36
but I'm suspecting that this or corrupted data or something I'm missing.
I've also read about TOAST-able and so on and I haven't messed with storage properties. The data into that columns aren't big numbers (maybe having many decimal counts)
Any clues? help?
Thank you
pgsql-admin
by date:
Previous
From:
Mariel Cherkassky
Date:
11 July 2018, 20:12:50
Subject:
Re: wal exist in slave but getting err requested WAL segment hasalready been removed
Next
From:
Mariel Cherkassky
Date:
11 July 2018, 20:19:43
Subject:
Re: invalid value for parameter "client_encoding": "ISO_8859_8"
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies