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
Re: BRIN indexes - TRAP: BadArgument - Mailing list pgsql-hackers
From
Jeff Janes
Subject
Re: BRIN indexes - TRAP: BadArgument
Date
November 5, 2014
22:58:39
Msg-id
CAMkU=1w=GiRci4HROAh64-M8sJuxgEb4qM+A9G-2QPkdh5YXJw@mail.gmail.com
Whole thread
Raw
In response to
Re: BRIN indexes - TRAP: BadArgument
(Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses
Re: BRIN indexes - TRAP: BadArgument
List
pgsql-hackers
Tree view
On Wed, Nov 5, 2014 at 12:54 PM, Alvaro Herrera
<
alvherre@2ndquadrant.com
>
wrote:
Thanks for the updated patch.
Now when I run the test program (version with better error reporting attached), it runs fine until I open a psql session and issue:
reindex table foo;
Then it immediately falls over with some rows no longer being findable through the index.
-- use index
select count(*) from foo where text_array = md5(4611::text);
0
-- use seq scan
select count(*) from foo where text_array||'' = md5(4611::text);
1
Where the number '4611' was taken from the error message of the test program.
Attachment
brin_crash.pl
pgsql-hackers
by date:
Previous
From:
Andres Freund
Date:
05 November 2014, 22:43:42
Subject:
Re: tracking commit timestamps
Next
From:
Josh Berkus
Date:
05 November 2014, 23:15:37
Subject:
Re: Amazon Redshift
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
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