thing like ORDER BY a COLLATION en_US, b COLLATION
es_US). This would perform passably on glibc but abysmally on most other
libc's.
>From that point forward we would go about adding support for strcoll_l() and
other interfaces to handle case (d) on various platforms. For platforms with
no
any particularly clean
solutions I think.
AFAIK the state of the art is actually to load the data into a table which
closely matches the source material, sometimes just columns of text. Then copy
it all to another table doing transformations. Not impressed.
--
Gregory Stark
Enterprise
ot clear is that it's easier to think of
cursors as being *between* rows rather than *on* rows. I'm not sure the
standard entirely adopts that model however.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sen
em
contradictory). However I'm skeptical about Simon's premise. It's not clear
any changes to ANALYZE here are at the expense of other proceses. Any cycles
saved in ANALYZE are available for those other processes after all...
--
Gregory Stark
EnterpriseDB http://www.ente
-ISO syntax to supported syntax.
I don't know what this refers to but it doesn't sound like the kind of thing
Postgres gets involved in.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hacke
y'll be ephemeral.
And the patch authors are unlikely to see them unless they're also doing
reviews.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent via pgsq
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>>
>> Bruce, you seem to have removed one of my three patches from the queue. I
>> would actually prefer you remove the other two and put back that one. It's
>> the
>> o
ce is still much less
severe than using a smaller-than-optimal prefetch size.
This is on a piddly little 3-way raid. On a larger raid you would want even
larger prefetch sizes.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA ser
to 0 (or effective_spindle_count to 1 depending on
which version of the patch you're reading) as well.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> On Fri, 2008-03-28 at 09:08 +, Gregory Stark wrote:
>
>> A more invasive form of this patch would be to assign and pin a buffer when
>> the preread is done. That would men subsequently we would have a pinned
>&g
g towards the more invasive buffer
manager changes myself.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
pper case) according to your preference.
It can only be set for driver and database handles. For statement handles
the value is frozen when prepare() is called.
So if you've always been using unquoted identifiers you can set
FetchHashKeyName to NAME_lc and it would contin
s possible Windows is swapping out
shared memory making having large shared memory segments dangerous on that
front.
Of course it's also possible something more subtle is going on.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slo
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Uhm, yeah, I somehow didn't write was I was thinking. I didn't mean to say we
>> would be taking a new snapshot for each INSERT but that we would be resetting
>
hot for each INSERT but that we would be resetting
xmin for each INSERT. Whereas currently we only set xmin once when we set the
serializable snapshot.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Sent via
.
Consider a data loading job which has millions of INSERT statements in a file.
Currently if you put them all in a transaction it takes a single snapshot and
runs them all with the same snapshot.
If you reset xmin whenever you have no live snapshots then that job would be
doing that between ever
t;
> If I really want to do this, it's going to turn into quite an overhaul
> of record handling in PG. It would also remove the nice syntactic trick
> that a.b identifies the field "b" from table "a", and s.a.b means that
> the above is in schema "s".
"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 d
OVER j though.
I suspect it will look more like the DISTINCT ON solution than the min(record)
solution.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq
saved --
in some cases that's not the right person. And the "reviewer" is just the
author of the last comment.)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
--
Sent vi
simple cases.
But I'm more eager to see full OLAP window functions which would let you do
this and a whole lot else as well.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-hackers mai
hem petered out was precisely because they
*don't* exactly line up with the semantics of sequences so I don't imagine
attempting to shoehorn sequences into these clauses is likely to pan out.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseD
Huh, fascinating. it's actually an RSS feed.
I can fool around with this. I should be able to snarf in the mbox and format
a wiki page with the comments from js-kit and links to the message-id.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Enterpr
that we had a URL we
could pass a message-id to. I think we all agreed that would be a wonderful
thing to have regardless of how we tackle this list anyways.
Magnus or Dave? Is there anything I can help with to get the URL to
message-ids going?
--
Gregory Stark
EnterpriseDB htt
to add links back to the
messages in the archive and ran into a problem with that. It also would have
been a pain because Bruce's list is divided up into pages.
If we modify the archives to have a URL to go straight to a message-id and
Bruce generated a list all on one page inclu
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> I wonder how useful it is to output process ids at all. And for that matter
>> whether leaking process ids alone could be considered a security risk.
>
> Seems ov
ld be considered a security risk. Perhaps
the error message should just output enough detail to uniquely identify the
log message.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
-
Sent via pgsql-hack
s pages to do that reasonably.
The "list" is at http://momjian.us/cgi-bin/pgpatches
It would be nice if we could remove the patches which have been reviewed or
applied from that list, but only Bruce can do that. Tom's berated Bruce once
for not focusing on the commitfest so I suspec
over to a
single disk sort of all the remaining tuples?
Also, I wonder how expensive checking the level break key on every tuple will
be. I don't think it invalidates the approach but it has to be taken into
account.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
her 16-bytes on every one of those updates is ok, but without the ability
to run vacuum.
Also, we still have hope that the visibility map info will make running vacuum
even less of an imposition.
All that said I don't really see much reason not to make it an option. I just
don't think
page of the key we're inserting while we perform the uniqueness check.
Could you still do that in this case? I don't immediately see any problems
aside from reduced concurrency but this code isn't really my forté.
--
Gregory Stark
EnterpriseDB http://www.enterprise
;ll go with TextPGetCString
> and CStringGetTextP.
I would have voted for text_to_cstring etc. I can see the logic for the above
but it's just such a pain to type...
Fwiw I didn't actually find text_cstring confusing because all our sql cast
functions are defined that way.
--
Grego
that
nobody should be interested in any more. If you locked the table and magically
deleted those tuples and updated the master tuple using the global xmin
instead of your real xid people would get the same result and you could
reclaim the space much much sooner. Locking the table kind of sucks tho
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> Nested Loop (cost=5.39..198.81 rows=51 width=244)
>>> -> HashAggregate (cost=1.06..1.11 rows=5
a monster
> query with lots of CASEs. I think we can and must do better.
Do we have something more helpful than "branches 3 and 5"? Perhaps printing
the actual transformed expressions?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by B
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> I already demonstrated that we could.
>
>> We seem to be talking past each other. The plan you showed
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> I don't understand which part of "we can do that now" isn't clear to you.
>
>> U
is would tend to reduce that. On the
other hand it would drastically increase the number of directory files the OS
has to keep track of and the total number of inodes being referenced.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS
ckers. For the -patches is
there mainly to catch large attachments regardless of their maturity.
But it's true that it's best to post a plan and have discussion prior to
developing big patches.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> It would be ideal if it could scan the invoices using an index, toss them all
>> in a hash, then do a bitmap index scan to pull out all the matching detail
>> records.
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> It would be ideal if it could scan the invoices using an index, toss them all
> in a hash, then do a bitmap index scan to pull out all the matching detail
> records. If there are multiple batches it can start a whole new ind
would very much like such a URL as well. At a guess it would require hacking
the tsearch parser we use for the search engine on the web site?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-h
advantages without buying into
> the restrictions that special space would have.)
One advantage of using separate relfilenodes would be that if we need to
regenerate a map we could do it in a new relfilenode and swap it in like we do
with heap rewrites.
--
Gregory Stark
EnterpriseDB
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> Please give an example of what you're talking about that you think we
>>> can't do now.
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> We currently execute a lot of joins as Nested Loops which would be more
>> efficient if we could batch together all the outer keys and execute a single
>> inner
;m trying to do is get a page which has the message-id's of all the
messages and the comments on the same page. That way I can dump the data into
a text file to experiment with.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Rep
d MD5 permanent
> link at the top of each message, e.g.:
>
> http://momjian.us/mhonarc/patches/msg00054.html
Any chance we could put that on the actual listing page somehow. perhaps in a
tiny font?? I want to be able to copy the thread and get enough information
for future refe
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Actually, is it just me or has the whole patch queue disappeared?
>> Everything under /mhonarc/patches seems to be gone.
>
> /mhonarc? The URL I've always use
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>> "Bruce Momjian" <[EMAIL PROTECTED]> writes:
>>
>> > bruce wrote:
>> >> > Yea, that is a big problem because the URLs are dynamic. I have the
>>
ches/dded9117101d6b0e1b8357066b9df9cd.html
>
> So _now_ it is permanent. ;-)
Not Found
The requested URL /mhonarc/patches/dded9117101d6b0e1b8357066b9df9cd.html was
not found on this server.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Ente
could use some help with reviewing.
Could you point me at a patch you think would make a good candidate? Or should
I just pick a random one?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers ma
romised the client the data is committed.
Surely we can't lose after the fsync? Losing at commit rather than at the time
of insert might still be poor, but how could we lose after we've promised the
data is committed?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
As
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> The output of aclitem can't be read back back in as an aclitem:
>
>> postgres=# select relacl::text from pg_class limit 1;
>> relacl
>> ---
"Tom Lane" <[EMAIL PROTECTED]> writes:
> I think this is a "must fix" bug for 8.3.1, anyone disagree?
Agreed.
It seems we should collect cases like this for the regression tests. The only
one I was aware of previously was the Turkish one.
--
Gregory Stark
ight now but I'll poke my nose in a bit later when
I'm done what I'm doing.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make chang
he incremental changes. To do this would require some magic to know
what "incremental changes" means for each aggregate where it's meaningful
though.
Then it would require some magic in the optimizer to recognize when piece of
the query can be satisfied by a materialized view.
--
cussion.
That's not to say we don't need designated maintainers to own specific pages.
But that's more of a positive assertion that if nobody else is doing something
they're responsible for getting it done rather than a negative assertion that
nobody else should be helpi
he 64-bit commandid anywhere which would be
the actual hard part.
Do "phantom" command ids mean this all just works magically? Ie, the limit of
2^32 pairs is still there but as long as you don't have to store
more than that many you get to have 2^64 raw ephemeral com
size of the arrays. Ie, allow people to specify larger
sample sizes and discard unreasonably large excess data (possibly warning them
when that happens).
That would remove the screw case the original poster had where he needed to
scan a large portion of the table to see at least one of ever
on the next step. As a result many patches kind of get stuck in a
catch-22 where they're not ready for review and no ready for development
either.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's
any
convenient way. I can see getting a single buffer of read-ahead from the index
block's next pointer but that's about it. Luckily it seems to me that bitmap
index scans are much more likely to be chosen in the cases where there's a big
gain anyways.
--
Gregory Sta
got involved here though since I specifically do not have
either the full context of this discussion or any background in
pg_dump/pg_restore code.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
n some bugs with sigint handling so I've been thinking of
rewriting it.
I think this is a low-hanging fruit which would help a lot of users. The
ability to load multiple COPY dumps would be the other piece of the puzzle but
personally I'm not sure how to tackle that.
quest. Etc.
Perhaps looking at the standard database SNMP MIB counters would give us a
place to start for upward facing events people want to trace for databases in
general.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Enterpr
function and all the items above it account for 7.25% of CPU.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, ple
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> How so? If you think this change is a bad idea you'd better speak up
>>> PDQ.
>
>> We
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> I'm intending to get rid of ~=~ and ~<>~ for 8.4; there's no longer any
>>> reason
domain where pgbouncer (or others
like it) is a good idea. Or you could pool or batch at a higher level and have
fewer sessions active at all. You don't win any performance by trying to do
more things simultaneously if they're just competing for cpu timeslices or i/o
bandwidth.
--
Gre
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Hm, for a simple = or <> I think it doesn't matter which operator class you
>> use. For < or > it would produce different answers. Postgres isn't cleve
lever enough
to notice that this is equivalent though so I think you would have to do
something like (untested):
CREATE INDEX new_index ON a (b text_pattern_ops) WHERE b ~<>~ '';
That uses the same operator that the LIKE clause will use for the index range.
--
Gregory Stark
E
[This message is mostly for the benefit of the list -- he and I already talked
a bit about this here at FOSDEM. Ishii-san, if you have a chance we should sit
down and talk about this in more detail before we leave!]
Tatsuo Ishii wrote:
>> On Tue, Feb 19, 2008 at 3:36 AM, Tatsuo Ishii <[EMAIL PRO
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> I can't say that I find this a nice clean solution; but does anyone have
>>> a better one?
>
&
ly more sane as well.
text* would just be a typedef to void* which could be passed to VARDATA_ANY
and VARDATA_ANY_EXHDR but not manipulated directly.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
et up in a similar way where custom.el edits a
separate file which you include from your .emacs.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP
"Andrew Dunstan" <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>> Also, I thought we said this would be an error:
>>
>> postgres=# select length("char"(0));
>> length
>> 0
>> (1 row)
>>
>>
>
m->length = out_len + VARHDRSZ;
Ah, that's not going to work in 8.3 any longer. You have to change this to:
SET_VARSIZE(im, out_len+VARHDRSZ)
And you have to access the length with VARSIZE_ANY_EXHDR() (or a few other
macros but that's the most convenient).
Phew. You had me scared
Also, I thought we said this would be an error:
postgres=# select length("char"(0));
length
0
(1 row)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's Postg
7;
(1 row)
postgres=# select "char"((random()*255)::integer+1);
ERROR: "char" out of range
postgres=# select "char"((random()*255)::integer+1);
ERROR: "char" out of range
--
Gregory Stark
EnterpriseDB http://www.enterprisedb
"Gregory Stark" <[EMAIL PROTECTED]> writes:
>> CREATE TYPE image (
>> INPUT = image_in,
>> OUTPUT = image_out,
>> INTERNALLENGTH = -1,
>> STORAGE = external
>> );
>
> ALTER column SET STORAGE EXTERNAL
or and didn't spot it.
I'll keep looking (or someone else will probably spot it before I do anyways)
but if these images are mostly incompressible data you would probably be
better off marking the columns as storage "external" so Postgres just toasts
them as-is instead of tr
shouldn't ever
happen because we don't store such data compressed.
I haven't quite figured out where the error is yet though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
trai
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
> On Tue, Feb 19, 2008 at 04:58:21PM +, Gregory Stark wrote:
>
>> The include file method is workable but isn't perfect. What happens if a user
>> connects with pgadmin and changes a parameter but that param
le which is overridden by the other source you can warn that the change
is ineffective.
I think on balance the include file method is so much simpler that I prefer it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about
ically whenever a seqscan happens or maintained by an index.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
One thing you might be missing is that indexes are relations too. They're a
bit different than heap relations (ie "tables") but they share enough
structure that it's worth using the same datatypes to represent both.
--
Gregory Stark
EnterpriseDB http://www.en
r judgement disagrees with others patches will just sit there with
everyone assuming someone else is looking at it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast
"Stephen Denne" <[EMAIL PROTECTED]> writes:
> i.e. Do I still have to either initdb --locale=C or explicitly use
> text_pattern_ops?
yes, if you want an index to be used
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Enterpri
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Gregory Stark wrote:
>> "Bruce Momjian" <[EMAIL PROTECTED]> writes:
>>
>> > For the patches lists I need to take sometimes entire threads, sometimes
>> > groups of comments, and
x27;s it.
The critical information we need are: What's the most recent version of the
patch? what is it blocking on? and who is it blocking on?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
---(end of broadcast)---
TIP 6: explain analyze is your friend
to maintain a queue of patches under consideration. They're two
separate, but related, things.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast)---
t; giving precedences to 270 or so currently precedence-less tokens
> just doesn't sound safe.
There are other rules that have a %prec on the rule itself, does that not work
here? *off to read the fine manual now*
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.c
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Sure, just like a + + b is ambiguous. We define an arbitrary choice and tell
>> people to put parentheses if they want the other. It's not too hard to write
>
I'm against overdesigned solutions. If we want more than a wiki I think it
would be reviewboard. I think something which fills a specific hole like
reviewboard is much more likely to work in the long term than an overarching
solution whose problem description is as vague as a "tracker"
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> But yeah, c_expr isn't enough. We really need {a,b}_expr sans postfix
>> expressions.
>
> How's that going to help? As long as postfix operators exist a
bit rusty.
Hm. I wonder if we could do a hack where we parse the a_expr ColId as a
regular a_expr and then check for that in the target_el rule or in parse
analysis and pull the ColId out.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by
wiki? I could
download the mbox files from the web site and filter them into a table.
Some part of me thinks this data should be in a postgres database so I can do
SQL queries against it to find a good patch to review.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
patch was against and of course e) if you make any changes they have
all the same problems dealing with your changes to their patch.
And it's hardly any more centralized than a distributed SCM system would be.
--
Gregory Stark
EnterpriseDB http://www.e
just
going to be queuing up for i/o requests or sitting runnable waiting for a
timeslice.
Was this with your patch to raise the size of the clog lru?
What is MaxBackends actually set to for the runs. Is it the same even when
you're actually running with fewer backends?
--
Gr
es").
git or its ilk would impact the lives of submitters and reviewers most.
Basically it would allow two non-committers to collaborate, something which we
can't really do effectively now.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask
ous FUD. Apply the logic in reverse
and it should be obvious. Subversion is a mature package being used by
thousands of open source projects. At this point I would hazard it's more
widely used than CVS amongst open source projects. Therefore it *doesn't* have
any poor choices of dependenc
601 - 700 of 1651 matches
Mail list logo
