Re: [HACKERS] Releasing in September

2016-01-21 Thread Marcin Mańk
On Wed, Jan 20, 2016 at 4:40 PM, Bruce Momjian wrote: > Many people where happy with our consistent releasing major releases in > September, e.g. 9.0 to 9.3: > > Not sure why the commitfest process should be synchronized with the release process. What if, when the release date comes, the currentl

Re: [HACKERS] high-dimensional knn-GIST tests (was Re: Cube extension kNN support)

2013-10-27 Thread Marcin Mańk
mpossible to get an improvement over sequential scan for 1000 dimensional vectors. Read here: http://en.wikipedia.org/wiki/Curse_of_dimensionality#k-nearest_neighbor_classification Regards Marcin Mańk

Re: [HACKERS] [patch] Proposal for \rotate in psql

2015-09-21 Thread Marcin Mańk
W dniu piątek, 18 września 2015 Daniel Verite napisał(a): > Pavel Stehule wrote: > > > in the help inside your last patch, you are using "crosstab". Cannto be > > crosstab the name for this feature? > > If it wasn't taken already by contrib/tablefunc, that would be a first > choice. But n

Re: [HACKERS] Checksums, state of play

2012-03-06 Thread Marcin Mańk
he_hint_bit_write(); Greetings Marcin Mańk -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] faster ts_headline

2012-11-20 Thread Marcin Mańk
filling in the applicable catalogs, and make the user make columns as hltext_element[]. Is there a nice way to manipulate objects of such a type from within the backend? Is there an example? I suppose that in this case storage would not be as efficient as I made it. which one to choose? Other ideas? Rega

[HACKERS] FATAL: ReleaseSavepoint: unexpected state STARTED

2011-08-17 Thread Marcin Mańk
connection unexpectedly This probably means the server terminated abnormally before or while processing the request. connection to server was lost The message is from 8.4.2, but the bug is in 9.0.4 too . Greetings Marcin Mańk -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgres

Re: [HACKERS] FATAL: ReleaseSavepoint: unexpected state STARTED

2011-08-18 Thread Marcin Mańk
avepoint: unexpected state STARTED server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. Greetings Marcin Mańk -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your su

Re: [HACKERS] [v9.2] make_greater_string() does not return a string in some cases

2011-09-23 Thread Marcin Mańk
One idea: col like 'foo%' could be translated to col >= 'foo' and col <= foo || 'zzz' , where 'z' is the largest possible character. This should be good enough for calculating stats. How to find such a character, i do not know. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.

Re: [HACKERS] Thoughts on "SELECT * EXCLUDING (...) FROM ..."?

2011-10-31 Thread Marcin Mańk
m too lazy to > type each column name out by hand". > How about an option for psql to truncate too long columns to X characters ? Greetings Marcin Mańk -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Term positions in GIN fulltext index

2011-11-03 Thread Marcin Mańk
l.org/docs/current/static/textsearch-debugging.html ts_debug does what You want, and more. Look at it's source - it`s a plain sql function, You can make something based on it. Greetings Marcin Mańk -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to you

Re: [HACKERS] synchronized snapshots

2010-01-09 Thread Marcin Mańk
that to send read-only queries to the standby, and when the first dml/ddl statement in a transaction comes up, they could switch to the master. If it is hard to tell from the statement if it writes anything, the pooler could catch the error, and retry on the master Regards Marcin Mańk

Re: [HACKERS] QSoC proposal: Rewrite pg_dump and pg_restore

2014-03-21 Thread Marcin Mańk
ion output. This would change the recommended "when upgrading, dump using the new pg_dump" to ""when upgrading, dump using the old pg_dump". This would be necessary policy going forward anyway, if most of the pg_dump functionality was server-side, because it would be genera