>> That may have been true until we started supporting Windows...
>> Swedish_Sweden.1252 is what I get on my machine, for example. Principle
>> is the same, but values certainly aren't.
>
> Well, at least the name is not itself translated, so a mapping table is
> not right out of the question. If
> Why not do it the other way around?
> es_ES spanish
> Spanish_Spain spanish
> ru_RU russian
> pt_BR portuguese_brazil
>
> That way you don't need any funny index. Or do you need the list of
> locales for each language? (but even if you do, you can easily obtain it
> by in
>> How would this work for initdb with locale C?
>
> I'm worrying about that too.
english '{en_GB, en_US, C}'
I suppose, that locale name always has a dot separator exept C locale ---
which is well known exception
---(end of broadcast)---
TIP 1
look at contrib/intarray. gist__intbig_ops is a variant of signature
tree (from each array get bitmap signature).
Regards,
Teodor
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Tom Lane wrote:
>
> Oleg Bartunov <[EMAIL PROTECTED]> writes:
> > Teodor finally made patches to current CVS, please review and apply them asap
> > to be in sync with development (last time it was kind of problem)
>
> Checked and committed. Note I did not
#x27;t it be better
to just make the initial condition of the for() look i = 1 ?
done
I'd like to review more, but it feels like a job that's more difficult than it
needs to be due to lack of comments.
Would it be possible to update the patch to try and explain things a litt
fail on
FreeBSD 10.2. Now I will try to run kind of TPC-H with and without patch.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@pos
(and a lot of other things) are getting left for later.
Agree
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
2
HT), FreeBSD 10.2.
pgbench -c 4 -j 4 -P 1 -T 60 -S
HEAD 35834 tps avg (35825/35828/35808/35844/35865)
Patched HEAD 35529 tps avg (35516/35561/35527/35534/35510)
~1% slowdown. I can live with that.
--
Teodor Sigaev E-mail: teo...@siga
One more inconsistence:
# select parse_ident(E'"\005"') as "\005";
\005
{\x05}
Display outputs of actual identifier and parse_indent are differ.
Actually, I can live with both but are any other opinions? Seems, at least
difference of actual identifier and outpu
vector and
tsvector_to_array to have consistent name. Later we could add
to_tsvector([regconfig, ], text[]) with morphological processing.
Thoughts?
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www
I saw errors on windows, here is the fix:
Thank you, pushed
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make
ROR: identifier contains disallowed characters: "\"c"
Error message wrongly points to the reason of error.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
parse_ident-13.patch
De
I hope so the messages are ok now. Few more regress tests added.
Thank you, committed.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql
because they are presented in auto-generated file
./src/include/utils/builtins.h
range patch is unchanged, but still attached to keep them altogether.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.si
Good catch, thanks! Tests were added.
I don't see any objection, is consensus reached? I'm close to comiit that...
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent
nges how 'width' is computed.
fixed too
So I think this way of building the index path from a BitmapOr path is
pretty much a dead-end.
I don't think so because separate code path to support OR-clause in index will
significanlty duplicate BitmapOr gene
ion has none.
added
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
0001-idx_or_core-v4.patch.gz
Description: GNU Zip compressed data
0002-idx_or_indexes-v4.patch.gz
Description: GNU Zip compresse
ut I won't get to it before weekend.
So, per patch status:
create-am
ready
generic-xlog
need to fix comments/docs
bloom-contrib
need review. I'm an original author of this module and of course
I can do some review of it but, seems, it's
DatumGetBoxP(in->scankeys[i].sk_argument),
+p_query_rect
+);
I don't think this matches the project coding style.
fixed
+ int flag = 1,
Wouldn't it be better as "bool"?
fixed.
The regress
tend to think of a *point* as having *zero* dimensions. Would it
perhaps be more accurate to say we are treating a 2-dimensional box
as a point in 4-dimensional space?
Exactly, sorry for ambiguity.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
help GiST. See Oleg's message.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your sub
in->allTheSame)
Most of the things happening before this check is not used in there.
Shouldn't we move this to the top of the function?
yep, fixed
+ out->nodeNumbers = (int *) palloc(sizeof(int) * in->nNodes);
This could go before allThe
t for libicu with configure flag
--with-icu. Patch rebased to current HEAD, hope, it works.
It's based on https://people.freebsd.org/~girgen/postgresql-icu/readme.html
work, and it was migrated to 9.5 with abbrevation keys support.
Patch in current state is not ready to commit, of course.
Does that mean this patch should be closed or is there more remaining to commit?
Petr promises to check english in comments/docs in generic-wal patch at this
week, bloom patch depends on it. Bloom patch is ready from my point of view.
--
Teodor Sigaev E
src/backend/access/transam/generic_xlog.c...)
Patching file src/backend/access/transam/generic_xlog.c using Plan A...
patch: malformed patch at line 634: diff --git
a/src/backend/access/transam/rmgr.c b/src/backend/access/transam/rmgr.c
--
Teodor Sigaev E-mail
I incorporated your changes and did some additional refinements on top of them
still.
Attached is delta against v12, that should cause less issues when merging for
Teodor.
But last version is 13th?
BTW, it would be cool to add odcs in VII. Internals chapter, description should
be similar to
ful example for such feature.
- add callback via RegisterResourceReleaseCallback() which will cleanup state
of genericXlogStatus variable
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Se
cussion is about SQL-level types which could be stored on disk, not
about in-memory structs
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgs
ssing and also added support for
them. It is also attached with the updated version of my test script.
I hope I haven't changed the patch too much. I have also pushed the
changes here:
https://github.com/hasegeli/postgres/commits/box-spgist
--
Teodor Sigaev
g patch itself:
1 trgm2.data contains too much duplicates (like Barkala or Bakalan). Is it
really needed for testing?
2 I'm agree with Jeff Janes about <<-> and <->> operation. They are needed.
(http://www.postgresql.org/message-id/CAMkU=1zynkqfkr-j2_uq8lzp0uho8i+le
ng at which the most similar match to the 1st argument occurs?
select substring_similarity_pos('dog' , 'hotdogpound') ;
answering: 4
Interesting, I think, it will be useful in some cases.
We could call them <<-> and <->> , where the first corresponds t
tions | weights
+---+-
a | {1} | {D}
b | {}| {}
I think, it's better to return NULL in this case
5
array_to_tsvector/tsvector_setweight_by_filter/tsvector_delete_arr/tsvector_filter
doesn't check or pay attention to NULL elements in input arra
Some notices:
1 tsin in documentation doesn't look like a good name. Changed to vector similar
to other places.
2 I did some editorization about freeing memory/forgotten names etc
Ooops, forgot to attach
--
Teodor Sigaev E-mail: teo...@siga
ted.
With the 3rd argument, we let the user decide what they want
to see.
3. This code is longer, so some regress tests are recommended - attached
simple test case
I've added a few regression tests to the psql testsuite
based on your sample data. New patch with these tests
included is
yyyy')
as a ;
length | length
+
414 | 63
--
Teodor Sigaev E-mail:
to me that Artur's patch is
good idea. Actually, I don't remember exactly, but, seems, commit
7ac8a4be8946c11d5a6bf91bb971b9750c1c60e5 introduced parse_affentry() instead of
corresponding sscanf to avoid problems with encoding and scanf.
--
Teodor Sigaev
ke to see a short comment describing at least new functions
5
Pls, add tests for new code.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hac
similarity is confusing name, but actually it search
most similar word in second arg to first arg and returns their similarity.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
y, it finds most similar word (not substring!)
from whole string. word_similarity? word_in_string_similarity?
substring_similarity_pos() could be a separate patch.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WW
this thread
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org
Thank you, committed
Jim Nasby wrote:
On 1/2/16 5:57 PM, Jim Nasby wrote:
Attached patch clarifies that %-related error messages with hints as
well as (IMHO) improving the clarity of the message:
Sorry, forgot to update regression tests. New patch attached.
--
Teodor Sigaev
make, but I don't see any
particular reason why we've got to make those decisions now.
+1
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list
On Thu, Feb 11, 2016 at 9:56 AM, Teodor Sigaev wrote:
1 - sml_limit to similarity_limit. sml_threshold is difficult to write I
think,
similarity_limit is more simple.
It seems to me that threshold is right word by meaning. sml_threshold is my
choice.
Why abbreviate it like that? Nobody&#
On 2/12/16 8:20 AM, Eugene Kazakov wrote:
TAP-tests need two Perl modules: Test::More and IPC::Run.
I think those modules are part of a standard Perl installation.
IPC::Run is not. At least for perl from ports tree in FreeBSD.
--
Teodor Sigaev E-mail: teo
ly and store them in traversalValue, available
when traversing child nodes, because otherwise we would't be able to
calculate them from inside the inner_consistent function call.
This patch was written by Teodor Sigaev.
* [PATCH] change reconstructValue -> traversalValue in range_spgi
it should
restricted to superuser obly.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscrip
X""X
Time: 0,510 ms
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chan
t-variable]
BloomPageOpaque opaque;
11 I'd really like to see regression tests (TAP-tests?) for replication with
generic xlog.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev
alone_cleanup patch is faster because regular insert could break its
cleanup process if autovacuum waits to begin work on cleanup. So, insert process
could returns earlier from pending cleanup process.
In attachment just rebased v2 alone_cleanup patch.
--
Teodor Sigaev
s it
does pending_lock patch but attached patch doesn't touch a lock management.
Tomas. if you can, pls, repeat test with this patch. If not, I will try to do
it, but later.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
PING FOR asciiword WITH xx,
english_stem;
# select to_tsvector('english', 'bookings');
to_tsvector
--
'book':1 'booking':1
# select to_tsvector('english', 'bookings') @@ '
paranoic and do this same way as before. Revised patch is
attached.
I see the change was done in 9.6 release cycle in commit
48354581a49c30f5757c203415aa8412d85b0f70 at April, 10. Does it mean the fix
should be backpatched too?
--
Teodor Sigaev
000;
if (xidWarnLimit < FirstNormalTransactionId)
xidWarnLimit -= FirstNormalTransactionId;
Why does it use '-' instead of '+' if variable < FirstNormalTransactionId? In
this case it is easy to get xidStopLimit > xidWrapLimit or xidWarnLimit >
xidStopLimit...
Thank y
8 bytes
(actually, it will be a varlena header!)
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http
from string collection
instead of JEntry array, JEntry array will be placed at the end of
object/array. so, pg_lzcompress will find repeatable 4-byte pieces in
first 1024 bytes of jsonb.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW:
:not tested
As I can see, this bugfix was already discussed and reviewed.
All mentioned issues are fixed in the latest version of the patch
So I mark it "Ready for committer".
Thank you for fixing it!
The new status of this patch is: Ready for Committer
--
Teo
om
ginVacuumPostingTree() and patch should just remove lock for cleanup over
ginVacuumPostingTreeLeaves() and if it returns that tree contains empty page
then lock the whole posting tree to do ginScanToDelete() work.
--
Teodor Sigaev
but isn't better to have another
protection? Like WAL-logging of WAL segment removing...
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-h
EmptyChild? and hasNonEmptyChild (BTW, isAnyNonempy has missed 't')
And if the whole posting tree is empty,then we could mark root page as leaf and
remove all other pages in tree without any locking. Although, it could be a task
for separate patch.
--
Teodor Sigaev
Thank you, pushed
Andrew Borodin wrote:
2017-03-22 22:48 GMT+05:00 Teodor Sigaev :
hasEmptyChild? and hasNonEmptyChild (BTW, isAnyNonempy has missed 't')
Yes, I think this naming is good. It's clear what's in common in these
flags and what's different.
And if
ed to 9.6?
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresq
Hmm, it doesn't work (but appplies) on current HEAD:
% uname -a
FreeBSD *** 11.0-RELEASE-p8 FreeBSD 11.0-RELEASE-p8 #0 r315651: Tue Mar 21
02:44:23 MSK 2017 teodor@***:/usr/obj/usr/src/sys/XOR amd64
% pg_config --configure
'--enable-depend' '--enable-cassert' &
g = false;
- st->is_throttled = false;
memset(st->prepared, 0, sizeof(st->prepared));
}
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing l
Thank you all, pushed
Michael Paquier wrote:
On Fri, Mar 24, 2017 at 1:45 AM, Teodor Sigaev wrote:
I believe patch looks good and it's ready to commit.
Thanks for the review!
As I understand, it fixes bug introduced by
commit 7117685461af50f50c03f43e6a622284c8d54694
Date: Tue Apr
.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql
free from point of view of pgStatTabList.
4 step 2. The same as 1) about SeenRelsEntry->rel_id but it even isn't
initialized anywhere.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.
Sorry, 1) and 4) is my fault, comment in hsearch.h:
* ... The hash key
* is expected to be at the start of the caller's hash entry data structure.
Ops, forgot that.
Teodor Sigaev wrote:
things in order I'm attaching the previous patch as well.
Patches look good, but I have some n
No, it is really needed so that the lag measure is correct.
Thank you, pushed
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers
.
If something should be done in this area, that would be surely in
fsync_fname directly to centralize all the calls, and I would think of
that as a separate patch, and a separate discussion.
Agree
--
Teodor Sigaev E-mail: teo...@sigaev.ru
Thank you, pushed
Michael Paquier wrote:
On Fri, Mar 24, 2017 at 11:36 PM, Teodor Sigaev wrote:
And the renaming of pg_clog to pg_xact is also my fault. Attached is
an updated patch.
Thank you. One more question: what about symlinks? If DBA moves, for
example, pg_xact to another dist and
to tab-complete.c that
is a shame I didn't do it before, very sorry about that.
Attached the new version of the patch that is basically the same as previously
with the addition to tab completion for psql and rebased with master.
Hope it is enough. Thank you all.
--
Matheus de Oliveira
Thank you, pushed
Excellent! I've attached a new (and hopefully final)
version of the patch.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (
this thread about naming and both databases, which
support covering indexes, use INCLUDE keyword.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql
both patches?
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
0001-covering-core.patch
Description: binary/octet-stream
0002-covering-btree.patch
Description: binary/octet-stream
--
Sen
dexes use it as opaque
type. Except, at least, btree and GiST - they believ that internal pointers are
the same as outer (to heap)
Another dubious part - BitmapScan.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
frz->t_infomask &= HEAP_XMAX_COMMITTED;
Seems, in last line it should be a bitwise OR instead of AND. Now this line
cleans all bits in t_infomask which later will be copied directly in tuple.
--
Teodor Sigaev
WLockPadded *) ShmemAlloc(sizeof(LWLockPadded) *
nslots);
Attached patch fixes that by removing extra ShmemAlloc for SLRU.
--
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
--
Teodor Sigaev
It's not clear from the web site in question that the relevant code is
released under the PostgreSQL license.
As author I allow to use this code in PostgreSQL and under its license.
--
Teodor Sigaev E-mail: teo...@siga
ult on seqscan variable.
Dump to reproduce (subset of real data but obfucated), queries are in attachment
http://sigaev.ru/misc/exists_to_nested.sql.gz
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sig
Both 9.6 and 10devel are affected to addiction of query result on seqscan
variable.
Oops, I was too nervious, 9.6 is not affected to enable_seqscan setting. But it
doesn't push down condition too.
--
Teodor Sigaev E-mail: teo...@siga
Ah, thanks for the clue about enable_hashjoin, because it wasn't
reproducing for me as stated.
I missed tweaked config, sorry
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers ma
development
and should wait for v11. Opinions?
Obviously, I'm voting for second patch applied to version 10.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers
ize (cost=0.00..1.40 rows=1 width=8) (actual time=0.000..0.001
rows=17 loops=1048576)
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
Timing is on.
DROP TABLE
Time: 5,268 ms
SELECT 32
T
come from a real
world case? else, how did you stumble upon it?
Unfortunately, it's taken from real application.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql
Teodor, could you check if this patch fixes your real-world problem?
It works fine with original query, thank you. But some other query slowdowns for
~10% (9 secs vs 10 secs). Look at following part of plans of huge query:
without patch:
-> Nested Loop (cost=34.82..50.91 rows=1 width
There were old threads about considering a risk factor when estimating
plans, and I'm thinking this issue is the planner failing to do
exactly that.
I'm afraid it's tool late for v10
--
Teodor Sigaev E-mail: t
BTW, was the larger query plan that you showed (with a Materialize node)
generated by 9.6, or v10 HEAD? Because I would be surprised if 9.6 did
v10,
commit acbd8375e954774181b673a31b814e9d46f436a5
Author: Magnus Hagander
Date: Fri Jun 2 11:18:24 2017 +0200
--
Teodor Sigaev
n't commutate with itself, it has a commutator
~~. Patch assumes that @@ is self-commutator, but ~~ will use 'contsel' as a
restrict estimation. Suppose, we need to declare ~~ as deprecated and introduce
commutating @@ operator.
--
Teodor Sigaev
rn 0;
}
That works for clang ang gcc48 with flags -Wall -Wextra -ansi (or -std=c90)
without warnings, but doesn't work with -pedantic. Is that enough to to work
with other compilers?
--
Teodor Sigaev E-mail: teo...@sigaev.ru
c99 although gcc has support in c90. To disable this support it's
needed a flag -pedantic. Sorry.
The real question is do we want to. What's your use-case for this?
Just do not have a hardcoded values. It is too easy to make a mistake in
hardcoded value.
--
Teodor Sigaev
as 4d-point.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresq
debugging purposes that some tuples
have been deleted from a page.
..
If Heikki doesn't change his opinion then introduce new flag. Although I don't
think that we need to keep F_TUPLES_DELETED.
Teodor Sigaev E-ma
I could be used in simple configuration
for read-only clients. I faced with customers which manages two connections in
process - to master and to one of several slaves.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
ister buffers
GenericXLogRegister(0, buffer1, false);
GenericXLogRegister(1, buffer2, true);
first argument is a slot number, second is the buffer, third is flag indicating
new buffer
Why do we need a slot number? to replace already registered buffer?
--
Teodor S
performance tests?
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postg
ricXLogFinish. User's code could throw a error or
allocate memory between them and error will become a panic.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
--
Sent via pgsql-hackers m
Petr Jelinek wrote:
On 2015-09-07 17:41, Teodor Sigaev wrote:
Some notices:
1) create-am.3.patch.gz
As I understand, you didn't add schema name to access method. Why?
Suppose, if we implement SQL-like interface for AM screation/dropping
then we should provide a schema qualificatio
n without
microvacuum.
Time: 368,780 ms
Time: 69,769 ms
Time: 9,545 ms
Time: 12,427 ms
That's perfect, but I can't reproduce that. Suppose, because of "unused function
'gistkillitems'"
--
Teodor Sigaev E-mail: teo...@sigaev.ru
BTW, I slightly modify your test to provide more stable results.
--
Teodor Sigaev E-mail: teo...@sigaev.ru
WWW: http://www.sigaev.ru/
drop table test;
CREATE TABLE test (box box);
alter table test set
1 - 100 of 835 matches
Mail list logo
