Jaime Casanova wrote:
> this one looks good to me, the only adjust i made to the patch is
Thank you for your review!
---
Taro Minowa(Higepon)
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
On Tue, Jul 14, 2009 at 4:34 PM, Jaime
Casanova wrote:
> On Thu, Mar 26, 2009 a
, TimeLineID and ?
Best regards,
-
MINOWA Taro (Higepon)
Cybozu Labs, Inc.
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
Hi.
> fashion --- for instance, each page is read only once. Index scan will
> result in a random sequence of accesses to the heap. (Of course, it
> might have some order if the index is well correlated with the heap
> order, but most of the time that's not true.)
Thank you. I finally understan
an and Bitmap Scan scans index on
emp_no and they are almost same cost.
In addition Bitmap Scan creates a bitmap. So Bitmap Scan is a little bit slower?
Best regards,
-
MINOWA Taro (Higepon)
Cybozu Labs, Inc.
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
On Tue, Apr 28,
e, it may choose
better plans than now.
Or the second option is to show some hints to people who are doing
performance tuning.
(a) Write trace log when bitmap scans falls into "lossy" mode.
(b) Show "lossy" or not on Explain results.
Best regards,
-
MINOW
mains to be solved is
"How much extra cost should we add for lossy mode?".
Any ideas?
Best regards,
-
MINOWA Taro (Higepon)
Cybozu Labs, Inc.
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To ma
m_maxentries = work_mem * 1024L;
if (estimatedNumLows < tbm_maxentries) {
/* not lossy */
} else {
/* lossy : we may add some extra costs to total costs */
}
Any ideas how to do this?
Best regards,
-
MINOWA Taro (Higepon)
Cybozu Labs, Inc.
http://www.monaos.org/
http://code.
==
the negative points of bytea:
memory hungry.
slower than large objects.
1GB limitation.
the negative points of large objects:
ghost problem (no auto-delete).
unable to store number of objects greater than 2^32.
=========
s a user of database, I think contrib/lo is not the best way.
Because it's not a part of core PostgreSQL, users may forget to use them.
Or it is a little messy to use.
So I think we need to implement *Auto* delete functionality in PostgreSQL core.
Cheers.
-
Taro Minowa(Higep
.
(1) Define a new type for large object
Same as Plan A. (unnecessary ?)
(2) Delete on VACUUM
On VACUUM, we check all tables which have "lo type",
and delete un-referenced large objects.
We may add a option "deleting large objects automatically&quo
Hi.
> Since we are about to go to beta, it may be that no one is up for
> reviewing it right now. But I've added it to the CommitFest page for
> the next CommitFest.
Thank you.
I wait until the next CommitFest.
-
Taro Minowa(Higepon)
http://www.monaos.org/
http://code.goo
bar.b3; Type: COMMENT; Schema: public; Owner: taro
--
COMMENT ON COLUMN bar.b3 IS 'column of a composite type b3';
Would someone please review this?
Cheers.
-
Taro Minowa(Higepon)
Cybozu Labs, Inc.
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
On Tue, Mar 24, 2009 at 1
table.
> Do we support comments on composite types
If we do, I will also write a patch for it.
Cheers.
-
Taro Minowa(Higepon)
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
On Tue, Mar 24, 2009 at 11:10 PM, Bruce Momjian wrote:
> higepon wrote:
>> Hi.
&g
mp out COMMENT statements like following?
COMMENT ON COLUMN some_index.index_column1 IS 'Hello column1';
Can anybody give me some advice on this?
Best regards,
-
Taro Minowa(Higepon)
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
--
Sent via pgsql-hackers mailing
mp out COMMENT statements like following?
COMMENT ON COLUMN some_index.index_column1 IS 'Hello column1';
Can anybody give me some advice on this?
Best regards,
-
Taro Minowa(Higepon)
http://www.monaos.org/
http://code.google.com/p/mosh-scheme/
--
Sent via pgsql-hackers mailing
15 matches
Mail list logo
