-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On Tuesday, March 25, 2008 22:51:53 -0400 Bruce Momjian <[EMAIL PROTECTED]>
wrote:
> Uh, I think it is hard to make a case that 'createuser' is an
> appropriate name for a Postgres utility. On the other hand, we haven't
> had many complaints a
Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Where are we on this? Tom thinks we don't want this. TODO has:
> > * Prefix command-line utilities like createuser with 'pg_'
> > http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php
>
> It wasn't just me;
Brendan Jurd wrote:
> On 9/29/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> > I think we need more than one person's request to add this function.
>
> Well, I don't expect it would get requested. Most DBAs would likely
> look for the function in the docs, see it's not there and then just
> imple
Merlin Moncure wrote:
> On Mon, Mar 24, 2008 at 9:48 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
> >
> > Add to pl/pgsql TODO:
> >
> > o Consider invalidating the cache or keeping seperate cached
> > copies when search_path changes
> >
> > http://archives.postgresql.or
On Mon, Mar 24, 2008 at 9:48 PM, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
> Add to pl/pgsql TODO:
>
> o Consider invalidating the cache or keeping seperate cached
> copies when search_path changes
>
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg01009.php
Bruce Momjian <[EMAIL PROTECTED]> writes:
> Where are we on this? Tom thinks we don't want this. TODO has:
> * Prefix command-line utilities like createuser with 'pg_'
> http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php
It wasn't just me; quite a few people were dub
Added to TODO:
> * Consider transaction start/end performance improvements
>
> http://archives.postgresql.org/pgsql-hackers/2007-07/msg00948.php
> http://archives.postgresql.org/pgsql-hackers/2008-03/msg00361.php
---
S
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Neil Conway wrote:
>> If we're just updating MyProc->xmin, we only need to acquire
>> ProcArrayLock in shared mode, right?
> In fact, do you need a lock at all?
I think you probably do. GetSnapshotData needs to be confident that the
global xmin
This has been saved for the next commit-fest:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Martin Pihlak wrote:
> Howdy,
>
> Here's an updated version of the function stats patch. The biggest change is
Whilst fooling with bug #4058 I noticed that xml2's .c files were being
compiled without -g or any of the various warning flags we normally use.
I saw this:
gcc -I/usr/include/libxml2 -fpic -I. -I../../src/include -D_GNU_SOURCE
-I/usr/include/libxml2 -c -o xpath.o xpath.c
when I expected somet
On Wed, Mar 26, 2008 at 01:03:18AM +, Gregory Stark wrote:
> "Sam Mason" <[EMAIL PROTECTED]> writes:
> > The reason for the sub-select is only because SQL doesn't provide any
> > other way to name expressions. Hum, or at least this should work...
> > There doesn't seem to be any nice way of ge
Where are we on this? Tom thinks we don't want this. TODO has:
* Prefix command-line utilities like createuser with 'pg_'
http://archives.postgresql.org/pgsql-hackers/2007-06/msg00025.php
See for reference:
http://momjian.us/mhonarc/patches/[EMAIL PROTECTED]
One idea is
"Sam Mason" <[EMAIL PROTECTED]> writes:
> The reason for the sub-select is only because SQL doesn't provide any
> other way to name expressions. Hum, or at least this should work...
> There doesn't seem to be any nice way of getting fields out of a record!
>
> If I really want to do this, it's go
Neil Conway wrote:
On Tue, 2008-03-25 at 17:26 -0300, Alvaro Herrera wrote:
There is one hole here: contention on ProcArrayLock. Basically, for
simple transactions we will need to update MyProc after every command.
If we're just updating MyProc->xmin, we only need to acquire
ProcArrayLock in
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> As discussed on -hackers, I'm trying to get rid of some redundant code
> by creating a widely useful set of functions to convert between text
> and C string in the backend.
Applied with revisions --- the functions were modified as per recent
discussion,
On Tue, 2008-03-25 at 17:26 -0300, Alvaro Herrera wrote:
> There is one hole here: contention on ProcArrayLock. Basically, for
> simple transactions we will need to update MyProc after every command.
If we're just updating MyProc->xmin, we only need to acquire
ProcArrayLock in shared mode, right?
On Tue, 2008-03-25 at 17:26 -0300, Alvaro Herrera wrote:
> I've finished (hopefully) the code to handle a current list of open
> snapshots in a transaction. I'm now wondering how to put it to good use
> ;-) I'm not posting it yet -- first I want to get some feedback on the
> previous patch I pos
Tom Lane wrote:
Kurt Roeckx <[EMAIL PROTECTED]> writes:
On Tue, Mar 25, 2008 at 02:11:30PM -0400, Tom Lane wrote:
Excellent, I'll go back-patch that and we can see what else there is.
You still have panda set up to build with gcc 4.3, correct?
Yes, I just disabled some cr
Hi,
I had a chance to go through the Hash join code of Postgresql and had the
following thoughts.
- Currently postgres takes the heaptuple from the slot and creates and
minimal_tuple and copies it into the temp file.
I think the creation of minimal_tuple in the middle is a overhead which can
b
Hi,
I've finished (hopefully) the code to handle a current list of open
snapshots in a transaction. I'm now wondering how to put it to good use
;-) I'm not posting it yet -- first I want to get some feedback on the
previous patch I posted,
http://archives.postgresql.org/pgsql-patches/2008-03/msg
Le Tuesday 25 March 2008 17:57:11 Dragan Zubac, vous avez écrit :
> and we're using a procedure to match prefices (longest prefix
> match),with simething like:
>
> while tmp_length <= char_length(d_number) loop
>
> -- take the number and try to find it in prefix table
> -- if not found,decrease it
On Tue, Mar 25, 2008 at 07:54:17PM +, Gregory Stark wrote:
> "Sam Mason" <[EMAIL PROTECTED]> writes:
> > SELECT i, (MIN((j,k))).k AS ka, (MIN((mycode(j),k))).k AS kb
> > FROM tbl
> > GROUP BY i;
>
> The flip side is that if you want to get several fields based on min(j) the
> min(record) appro
"Sam Mason" <[EMAIL PROTECTED]> writes:
> On Tue, Mar 25, 2008 at 06:58:06PM +, Gregory Stark wrote:
> The main thing I wanted to avoid was an explosion of sub-queries that
> you get with DISTINCT ON style queries. For example, with record style
> syntax, I can do:
>
> SELECT i, (MIN((j,k))
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> On Tue, Mar 25, 2008 at 02:11:30PM -0400, Tom Lane wrote:
>> Excellent, I'll go back-patch that and we can see what else there is.
>> You still have panda set up to build with gcc 4.3, correct?
> Yes, I just disabled some cron jobs for those that failed.
Hi,
As said, i am attaching the performance test results and the same patch
in this thread works with the latest CVS head.
Actually, i am seeing a slight performance improvement with the patch, which
i think might be either because of noise/ lesser pages. i ran it with the
default settings. i
On Sat, 2008-03-22 at 21:24 -0400, Tom Lane wrote:
> Oh, wait, that's just a -patches entry; it doesn't look like Neil
> ever committed it. Neil, how come?
Sorry, slipped through the cracks -- I've now committed the patch.
-Neil
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
On Tue, Mar 25, 2008 at 06:58:06PM +, Gregory Stark wrote:
> "Sam Mason" <[EMAIL PROTECTED]> writes:
> > SELECT i, MIN(k) OVER (PARTITION BY j)
> > FROM tbl
> > GROUP BY i;
> >
> > This is obviously wrong, but I don't see how to get to where I need to
> > be.
>
> I'm not entirely sure my
Hello
there is some noises about my patches :(
I sent EXECUTE USING - it's important (against to SQL injection and
faster dynamic SQL), this patch is linger time in queue.
variadic function, named params exist only as WIP and I see it for
next commit fest. I'll send new version in next months.
>
> extern text *cstring_to_text_with_len(const char *s, int len);
buffer_to_text ???
Regards
Pavel Stehule
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
"Sam Mason" <[EMAIL PROTECTED]> writes:
> SELECT i, MIN(k) OVER (PARTITION BY j)
> FROM tbl
> GROUP BY i;
>
> This is obviously wrong, but I don't see how to get to where I need to
> be.
I'm not entirely sure myself. I think it might involve RANK OVER j though.
I suspect it will look more
On Tue, Mar 25, 2008 at 02:11:30PM -0400, Tom Lane wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > On Mon, Mar 24, 2008 at 05:59:33PM -0400, Tom Lane wrote:
> >> http://archives.postgresql.org/pgsql-committers/2007-03/msg00292.php
>
> > This patch atleast solves the problems with 8.2.
>
> Ex
Ok, AFAICT it is complete:
http://wiki.postgresql.org/wiki/CommitFest:March
It is a reasonably short page, so it's really easy to search for things
you might want to work on for this commit fest.
I also added the patches submitted on March 2008 to the May commitfest
page.
Patch submitters: plea
Kurt Roeckx <[EMAIL PROTECTED]> writes:
> On Mon, Mar 24, 2008 at 05:59:33PM -0400, Tom Lane wrote:
>> http://archives.postgresql.org/pgsql-committers/2007-03/msg00292.php
> This patch atleast solves the problems with 8.2.
Excellent, I'll go back-patch that and we can see what else there is.
You
Tom Lane escribió:
> "Brendan Jurd" <[EMAIL PROTECTED]> writes:
> > A text_to_cstring_with_len() or text_to_cstring_limit() might be more
> > to the point, and more consistent with the other functions in the
> > family.
>
> Hmm. The thing that's bothering me is that the length is the size
> of t
Tom Lane wrote:
> > A text_to_cstring_with_len() or text_to_cstring_limit() might be more
> > to the point, and more consistent with the other functions in the
> > family.
>
> Hmm. The thing that's bothering me is that the length is the size
> of the *destination*, which is not like cstring_to_te
On Mar 25, 2008, at 4:43PM, Gregory Stark wrote:
> On Mar 20, 2008, at 2:23 PM, Sam Mason wrote:
> > SELECT i, (MIN((j,k))).k
> > FROM tbl
> > GROUP BY i;
>
> I have nothing against having min(record) and it does seem like it would let
> you do this at least for reasonably simple cases.
The ma
On Mon, Mar 24, 2008 at 05:59:33PM -0400, Tom Lane wrote:
> Kurt Roeckx <[EMAIL PROTECTED]> writes:
> > I did try the patch. It fails just the same way.
>
> Hmph. So we still don't know why 8.2 and 8.3 behave differently ...
> [ pokes around ... ] Hah, maybe this is it:
>
> http://archives.post
"Brendan Jurd" <[EMAIL PROTECTED]> writes:
> On 26/03/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
>> ... What I think is more useful is
>> a strlcpy()-like function that copies into a caller-supplied buffer
>> of limited size. For lack of a better idea I propose defining it
>> *exactly* like strlcpy
On 26/03/2008, Tom Lane <[EMAIL PROTECTED]> wrote:
> Brendan's patch also included "cstring_text_limit(const char *s, int len)"
> which was defined as copying Min(len, strlen(s)) bytes. I didn't find
> this to be particularly useful. In the first place, all potential
> callers are passing the
Gregory Stark wrote:
> Hm, at the same time as you were doing this I wrote a perl script to dump
> Bruce's mail box into a table. The results are at:
Heh. I should have guessed.
> http://wiki.postgresql.org/wiki/CommitFest:Bruce
It is a lot harder to trawl though ... I think it's easier to f
Hello
Not so familiar with all this math :) ,but here's my solution,which I
must admit keep things going at the moment:
db=> \d prefix
Table "public.prefix"
Column | Type | Modifiers
--+-+--
Is anyone on hackers interested in touring Washington on Monday after PG
East? Magnus and I are planning to go. Please email me privately for
details.
--
Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
Andrew Dunstan wrote:
> >> Surely that there is an emerging consensus to that effect means that it's
> >> not as unfortunate as it might be? I seem to recall the original
> >> announcement suggesting this was an experiment. I wouldn't expect the
> >> first
> >> couple rounds to go without a hitc
"Alvaro Herrera" <[EMAIL PROTECTED]> writes:
> Hi,
>
> I created a page for our current commitfest:
>
> http://wiki.postgresql.org/wiki/CommitFest:March
>
> Not all patches are there yet. I only added the latest version of each
> patch. I'll continue after lunch.
>
> I also created one for the n
Tom Lane wrote:
Andrew Sullivan <[EMAIL PROTECTED]> writes:
On Mon, Mar 24, 2008 at 06:39:25PM -0400, Andrew Dunstan wrote:
perusing a mailbox again. We have unfortunately been badly underprepared
for this.
Surely that there is an emerging consensus to that effect means t
Zoltan Boszormenyi írta:
Simon Riggs írta:
On Tue, 2008-03-25 at 09:08 -0700, Steve Crawford wrote:
Simon Riggs wrote:
RESTART IDENTITY will reset the SERIAL sequences back to the original
start value.
Assuming this feature were to be added
In cases where the same sequence
"Sam Mason" <[EMAIL PROTECTED]> writes:
> On Mon, Mar 24, 2008 at 05:27:04PM -0500, Decibel! wrote:
>> On Mar 20, 2008, at 2:23 PM, Sam Mason wrote:
>> > SELECT i, (MIN((j,k))).k
>> > FROM tbl
>> > GROUP BY i;
>>
>> How is that any better than SELECT i, min(k) FROM tbl GROUP BY i ?
>
> Because
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> SQL200n specifies a new qualifier on a TRUNCATE command
>
> TRUNCATE TABLE foo
> [ CONTINUE IDENTITY | RESTART IDENTITY ]
>
> CONTINUE IDENTITY is the default and does nothing, like now.
>
> RESTART IDENTITY will reset the SERIAL sequences back to
Zoltan Boszormenyi wrote:
> All of them? PostgreSQL allow multiple SERIALs to be present,
> the standard allows only one IDENTITY column in a table.
> And what about this case below?
>
> CREATE TABLE t1 (id1 serial, ...);
> ALTER SEQUENCE seq_t1_id1 RESTART WITH 5432 CYCLE;
>
> or the equivalent
Simon Riggs írta:
On Tue, 2008-03-25 at 09:08 -0700, Steve Crawford wrote:
Simon Riggs wrote:
RESTART IDENTITY will reset the SERIAL sequences back to the original
start value.
Assuming this feature were to be added
In cases where the same sequence has been used across m
I've been working some more on Brendan Jurd's patch to simplify text <->
C string conversions. It seems we have consensus on the names for the
base operations:
extern text *cstring_to_text(const char *s);
extern char *text_to_cstring(const text *t);
Brendan's patch also included "cstring_text_li
On Mon, Mar 24, 2008 at 05:27:04PM -0500, Decibel! wrote:
> On Mar 20, 2008, at 2:23 PM, Sam Mason wrote:
> > SELECT i, (MIN((j,k))).k
> > FROM tbl
> > GROUP BY i;
>
> How is that any better than SELECT i, min(k) FROM tbl GROUP BY i ?
Because I want the value of k associated with the minimum v
Hi,
I created a page for our current commitfest:
http://wiki.postgresql.org/wiki/CommitFest:March
Not all patches are there yet. I only added the latest version of each
patch. I'll continue after lunch.
I also created one for the next commitfest:
http://wiki.postgresql.org/wiki/CommitFest:Ma
On Tue, 2008-03-25 at 09:08 -0700, Steve Crawford wrote:
> Simon Riggs wrote:
> > RESTART IDENTITY will reset the SERIAL sequences back to the original
> > start value.
> >
> Assuming this feature were to be added
>
> In cases where the same sequence has been used across multiple tables,
>
Hi,
I'm trying to code a GiST opclass to index prefix searches (select ... from t
where t.prefix @> query), now using a prefix_range datatype. This datatype is
a varlena one, and storing it to disk and indexing it with BTrees work ok,
but I'm failing to have my GiST opclass working, here's the
Simon Riggs wrote:
RESTART IDENTITY will reset the SERIAL sequences back to the original
start value.
Assuming this feature were to be added
In cases where the same sequence has been used across multiple tables,
what will be the appropriate response when a user attempts to TRUNCATE
one
On Tue, 2008-03-25 at 11:48 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > SQL200n specifies a new qualifier on a TRUNCATE command
> > TRUNCATE TABLE foo
> > [ CONTINUE IDENTITY | RESTART IDENTITY ]
>
> > CONTINUE IDENTITY is the default and does nothing, like now.
>
> >
On Tue, 2008-03-25 at 11:47 -0400, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Tue, 2008-03-25 at 10:45 -0400, Bruce Momjian wrote:
> >> Where does this FETCH appear in a SELECT?
>
> > It's supposed to go *after* the OFFSET clause in a query, but making it
> > a simple synonym
"Mihai Criveti" <[EMAIL PROTECTED]> writes:
> I've compiled PostgreSQL 8.3.1 using gcc 4.2.3 on HP-UX 11i v1, and all went
> well. PostgreSQL works and everything, except for psql client:
> /usr/lib/dld.sl: Unresolved symbol: tgetent (code) from
> /usr/local/lib/libreadline.sl
Kinda looks like y
On Tue, Mar 25, 2008 at 04:54:59PM +0200, Mihai Criveti wrote:
> I've compiled PostgreSQL 8.3.1 using gcc 4.2.3 on HP-UX 11i v1, and all went
> well. PostgreSQL works and everything, except for psql client:
>
> $ /usr/local/pgsql/bin/psql
> Welcome to psql 8.3.1, the PostgreSQL interactive termina
Andrew Sullivan <[EMAIL PROTECTED]> writes:
> On Mon, Mar 24, 2008 at 06:39:25PM -0400, Andrew Dunstan wrote:
>> perusing a mailbox again. We have unfortunately been badly underprepared
>> for this.
> Surely that there is an emerging consensus to that effect means that it's
> not as unfortunate a
Simon Riggs <[EMAIL PROTECTED]> writes:
> SQL200n specifies a new qualifier on a TRUNCATE command
> TRUNCATE TABLE foo
> [ CONTINUE IDENTITY | RESTART IDENTITY ]
> CONTINUE IDENTITY is the default and does nothing, like now.
> RESTART IDENTITY will reset the SERIAL sequences back to the ori
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Tue, 2008-03-25 at 10:45 -0400, Bruce Momjian wrote:
>> Where does this FETCH appear in a SELECT?
> It's supposed to go *after* the OFFSET clause in a query, but making it
> a simple synonym for LIMIT seems most sensible.
Huh? OFFSET isn't in standard
Russell Smith <[EMAIL PROTECTED]> writes:
> What makes this change particularly challenging? The fact that nobody
> has agreed on how it should work, or the actual coding?
Getting the right design is definitely challenging. The coding might or
might not be, depending on your design ...
A Dimarts 25 Març 2008, r&[EMAIL PROTECTED] va escriure:
> Hi all,
>
> Does anybody know if is it possible to store images in Postgre? If it is
> possible which data type should I use?
>
Yes it's possible, you can use BYTEA for this, for example. But please, this
kind of questions should go to us
I've compiled PostgreSQL 8.3.1 using gcc 4.2.3 on HP-UX 11i v1, and all went
well. PostgreSQL works and everything, except for psql client:
$ ldd /usr/local/pgsql/bin/psql
=>
/usr/lib/libc.2 => /usr/lib/libc.2
/usr/lib/libdld.2 =>/usr/lib/libdld.2
/usr/lib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 25 Mar 2008 12:06:09 -0300 (BRT)
r&[EMAIL PROTECTED] wrote:
> Hi all,
>
> Does anybody know if is it possible to store images in Postgre? If it
> is possible which data type should I use?
There are two ways to do it:
http://www.postgresql.o
Hi all,
Does anybody know if is it possible to store images in Postgre? If it is
possible which data type should I use?
Thanks in advance,
--
R&D | Alea Management & Technology Solutions
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription
On Tue, 2008-03-25 at 10:45 -0400, Bruce Momjian wrote:
> Simon Riggs wrote:
> > SQL200n specifies a new command similar to our LIMIT
> >
> > FETCH { FIRST | NEXT } n { ROW | ROWS } ONLY
> >
> > and also that the OFFSET command can have an optional suffix
> >
> > { ROW | ROWS }
> >
> > Seems li
On Mon, Mar 24, 2008 at 06:39:25PM -0400, Andrew Dunstan wrote:
> perusing a mailbox again. We have unfortunately been badly underprepared
> for this.
Surely that there is an emerging consensus to that effect means that it's
not as unfortunate as it might be? I seem to recall the original
annou
Bruce Momjian wrote:
>
> Added to TODO:
>
> * Improve detection of shared memory segments being used by other
> FreeBSD jails
>
> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00656.php
There's a bit more than that to it -- see
http://archives.postgresql.org/pgsql-hackers/2008-01/
Simon Riggs wrote:
> SQL200n specifies a new command similar to our LIMIT
>
> FETCH { FIRST | NEXT } n { ROW | ROWS } ONLY
>
> and also that the OFFSET command can have an optional suffix
>
> { ROW | ROWS }
>
> Seems like a % project for the TODO list
Where does this FETCH appear in a SELECT?
SQL200n specifies a new qualifier on a TRUNCATE command
TRUNCATE TABLE foo
[ CONTINUE IDENTITY | RESTART IDENTITY ]
CONTINUE IDENTITY is the default and does nothing, like now.
RESTART IDENTITY will reset the SERIAL sequences back to the original
start value.
Seems like a % project for
SQL200n specifies a new command similar to our LIMIT
FETCH { FIRST | NEXT } n { ROW | ROWS } ONLY
and also that the OFFSET command can have an optional suffix
{ ROW | ROWS }
Seems like a % project for the TODO list
--
Simon Riggs
2ndQuadrant http://www.2ndQuadrant.com
PostgreSQL UK 2
On Mar 20, 2008, at 2:23 PM, Sam Mason wrote:
I'm trying to write a version of the MIN aggregate for values of
RECORD
type. I'm somewhat stuck on getting type information about the
argument
out, I can determine how many attributes it's got but I can't seem
to do
any better than that. Does
On Tue, Mar 25, 2008 at 01:46:51PM +0100, Zeugswetter Andreas OSB SD wrote:
> > So, I finally decide to focus on the project idea of improving hash
> > index now. It's more valuable , and also challenging.
> >
> > Any suggestion about the project idea of improving hash index?
>
> Imho one thing t
Russell Smith wrote:
Tom Lane wrote:
Russell Smith <[EMAIL PROTECTED]> writes:
As an attempt at a first PostgreSQL patch, I'd like to see if I can
do anything about this issue.
Trying that as a first patch is a recipe for failure... the short answer
is that no one can think of a solu
Tom Lane wrote:
> The proper wording of this item is
>
> * Find a correct rint() substitute on Windows
Fixed.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-hackers mailing list (pgsql-hacke
Tom Lane wrote:
Russell Smith <[EMAIL PROTECTED]> writes:
As an attempt at a first PostgreSQL patch, I'd like to see if I can do
anything about this issue.
Trying that as a first patch is a recipe for failure... the short answer
is that no one can think of a solution that will be gener
> So, I finally decide to focus on the project idea of improving hash
> index now. It's more valuable , and also challenging.
>
> Any suggestion about the project idea of improving hash index?
Imho one thing to look into is the storage. I do not see any real value
in storing the key itself (espec
Tom Lane napsal(a):
Zdenek Kotala <[EMAIL PROTECTED]> writes:
Tom Lane napsal(a):
This is not happening, at least not without 100 times more work than
anyone has shown willingness to put into the issue.
I understand your arguments, but it is important for in-place upgrade.
No, it is not, y
Thank you for all of your advices.
I think you're right. I should be more realistic. There are so many
work to do if I want to do some work on Flash disk. It's too difficult
to complete the task only in a summer. Obviously, It's not an
appropriate project idea for GSoC anyway.
Maybe I'll do it in t
>
> On Tue, 25 Mar 2008, mx wrote:
>
> > The atom unit of flash is page(512~2048byte typically). Page are
> > organized into blocks, typically of 32 or 64 pages. All read write and
> > write operations happen at page granularity, but erase operations happen
> > at block granularity.
>
> You made a
83 matches
Mail list logo
