CT a.pk FROM a JOIN b USING (x)
into
SELECT a.pk FROM a WHERE x IN (SELECT x FROM b)
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
ossible joins to *add*. So even if the user writes
"select * from invoices where customer_id=?" the planner might be able to
discover that it can find those records quicker by scanning customer, finding
the matching and then using an index to look them up
in invoices.
--
G
"Tom Raney" <[EMAIL PROTECTED]> writes:
> This is an update to my EXPLAIN XML patch submitted a few days ago.
>
> I've added a documentation patch and modified some of the code per comments
> by
> Gregory Stark.
You should update the wiki at
http://wiki.po
values were found? If HTSV can hint xmin for a tuple but finds xmax still in
progress perhaps that's a good sign it's not worth dirtying the page?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's Post
ld be simpler to have a wrapper function HTSV() macro which
passes flexible=true to HTSV_internal(). Then vacuum can call HTSV_internal().
I'm not sure what the performance tradeoff is between having an extra argument
to HTSV and having HTSV check a global which messes with optimizations.
he dependencies between them. That's functionality that
isn't available elsewhere and can't be reproduced without just reimplementing
pg_dump.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsq
===
RCS file: /home/stark/src/REPOSITORY/pgsql/src/bin/psql/describe.c,v
retrieving revision 1.173
diff -c -r1.173 describe.c
*** src/bin/psql/describe.c 13 May 2008 00:23:17 - 1.173
--- src/bin/psql/describe.c 23 May 2008 18:52:57 -
**
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> Oleg pointed out to me here that while we have a command to *set* the toast
> storage characteristics there's no actual supported way to display the current
> settings.
>
> It seems like this would be a reasonable
ibe.c
===
RCS file: /home/stark/src/REPOSITORY/pgsql/src/bin/psql/describe.c,v
retrieving revision 1.170
diff -c -r1.170 describe.c
*** src/bin/psql/describe.c 5 May 2008 01:21:03 - 1.170
--- src/bin/psql/describe.c 21 May 2008 18:07:13
ry.
>
> statement_timeout :)
Good point.
Though it occurs to me that if you set FETCH_COUNT in psql (or do the
equivalent in your code ) statement_timeout becomes much less useful.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's
't have already.
The recursive query syntax in the spec actually does include the ability to
assign an output column to show what level of recursive iteration you're on.
So alternately we could have a GUC variable which just allows the DBA to
prohibit any recursive query without such
at concept with the join
plans like merge join or hash join which expect you to be able to be able to
process the records in a specific order?
It sounds like you might have to keep around a stack of started executor nodes
or something but hopefully we can avoid anything like that because, w
d the results. But that's not actually reliable. It's quite possible to
have clauses which will limit the output but not in a way the database can
determine. Consider for example a tree-traversal for a binary tree stored in a
recursive table reference. The DBA might know that th
"David Fetter" <[EMAIL PROTECTED]> writes:
> On Mon, May 19, 2008 at 12:21:20AM -0400, Gregory Stark wrote:
>> "Zoltan Boszormenyi" <[EMAIL PROTECTED]> writes:
>> > Also, it seems there are no infinite recursion detection:
>> >
>>
the top of \?.
>
> The purpose of 'help' is to provide useful help. If it only says "see \?"
> then it's just redirecting you somewhere else, which isn't useful.
Haven't been following this thread. Has the idea of making "help" just a
; the trusted flag as well.
I'm not so sure. What about if a PL language wants to include a version number
in the language handler? Or if a new version has to change the name for some
reason -- perhaps they discover that the old name doesn't work on some linkers
for so
\pset format html:autowrap
But I think we agree that isn't happening so why spell it "aligned:autowrap"
instead of just "wrap"?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
--
Se
HTML" for example, nor would we want there to
> be.)
Well there's no unaligned HTML or aligned unaligned either...
> I think that could be fixed easily by having the syntax be something
> like
>
> \pset format aligned:80
> \pset format aligned:autowrap
I suppose. I
27;t see any way not to kill v0 for non-integral types if we want to make
float4 and float8 pass-by-value. We could leave those pass-by-reference and
just make bigint pass-by-value.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand P
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>>> Tom Lane wrote:
>>>> Specifically, I think what you missed is that on some platforms C
>>>> functions pass or return float values differently from si
I for i386 does no such thing. You can get
behaviour like that from GCC using function attributes like regparam but it's
not the default.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony Replication support!
--
Sent via pgsql-pat
"Bryce Nesbitt" <[EMAIL PROTECTED]> writes:
> I asked the folks over at "Experts Exchange" to test the behavior of the ioctl
I always thought that was a joke domain name, like Pen Island.com.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
ll be
formatted with a line length appropriate to the
current terminal (using an ioctl(2) if available, the value of
$COLUMNS, or falling back to 80 characters if neither is available). Cat pages
will only be saved when the default formatting can
be used, that is when
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Also, how would you suggest figuring the width to use for output going to a
>> file? ioctl is irrelevant in that case, imho it should just default to 80
>> colu
he ioctl's going to get back but it's unlikely to be
right. In any case I may want to format the output to a width narrower than
the window because I'm going to narrow it.
Also, how would you suggest figuring the width to use for output going to a
file? ioctl is irrelevant in th
is have a separate program (I would write a client but a
server-side function would work too) to kick off users based on various
criteria you can specify.
Then you can put in your backup scripts two commands, one to kick off idle
users and then do a smart shutdown.
--
Gregory Stark
EnterpriseD
es
> pass by value instead of pass by reference.
There was a patch to do this posted recently here as well.
http://archives.postgresql.org/pgsql-patches/2008-03/msg00335.php
Hm. I suppose it's true that you could make Datum 64-bit even on 32-bit
machines and make int8 and float8 pas
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> I think a better way to get a real "percentage done" would be to add a method
>> to each node which estimates its percentage done based on the percentage done
>
"Heikki Linnakangas" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Gregory Stark <[EMAIL PROTECTED]> writes:
>>> There are downsides:
>>
>> Insurmountable ones at that. This one already makes it a non-starter:
>>
>>>
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> I know I should still be looking at code from the March Commitfest but I was
>> annoyed by this *very* FAQ:
>
>> http://archives.postgresql.org/pgsq
uch as BSD where the default will probably be C-t).
But no reviewing it until we finish with the March patches!
Do as I say, not as I do :(
explain-progress.diff.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Enterprise
verloading the comparison
function.
Then if the support function is there it supports that type of scan and if it
doesn't then it doesn't, rather than depending on a magic third argument to
completely change behaviour.
You can always share code using an internal function or if the behavi
han have to wait for the complete index scan to finish
before processing any. Is that it?
In general I think we need to be more open to incremental improvements. I
think there are several fronts on which we refuse patches to do X because it's
useless without Y and have nobody working on Y bec
hich case we wouldn't need an
uninstall script at all.
The hacks to do this seem pretty dirty but on the other hand the idea of
having modules consist of a bunch of objects rather than arbitrary SQL
actually seems cleaner and more robust.
--
Gregory Stark
EnterpriseDB http://www.
"Bruce Momjian" <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>> Gregory Stark wrote:
>> >
>> > Here's the WIP patch I described on -hackers to implemented "ordered"
>> > append
>> > nodes.
>>
>> D
record that the last checkpoint record *points to*.
That represents the "guarantee" that the database is making to the sysadmin
about data integrity. Everything before that time is guaranteed to have
reached data files already. Everything after it may or may not be in the data
files and has
"Bernd Helmle" <[EMAIL PROTECTED]> writes:
> --On Donnerstag, April 03, 2008 14:36:59 +0100 Gregory Stark
> <[EMAIL PROTECTED]> wrote:
>
>>> \o foo instead of \i foo -- check your keyboard layout
>>
>> The point is here you've typed a diffe
kages where packagename like :1
\setquery bbdb select * from bbdb where name like :1
\query deb postgres
\query bbdb peter
to run a saved query. I'm not attached to "setquery" though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
going?'
#= select 'what happened to my ldd file?'
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
k the same logic as \df applies for those other things too. \dt
pg_class should "just work". And if you create a macaddr data type it doesn't
seem like too much of an imposition to play it safe and have \dT macaddr show
the user that there are now two matching data types.
So I guess I
wful. Even if it's not implemented right away I think we
should figure out what the syntax would be for passing arguments to be
interpolated into the query before backing ourselves into a corner.
I can't imagine much of a use case for being able to alias backslash commands
themselves. Th
nd proposal.
I prefer it to my own first proposal or any of the others.
I admit I was thinking primarily of non-globbing cases for pattern. As in, I
would want \df rtrim to "work". I suppose it could be annoying to have to type
\df public.* -- there's nothing stopping us from
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> One --perhaps nice, perhaps not-- property of this is that if you defined a
>> function named "rtrim" and then did "\df rtrim" it would show you _both_
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> It might be cute to see if the pattern matches any user functions and if not
>> try again with system functions. So you would still get results if you did
>> "\df
ust your user functions. That's a real headache and it
gets worse as we add more and more system functions too.
It might be cute to see if the pattern matches any user functions and if not
try again with system functions. So you would still get results if you did
"\df rtrim&
ction which needs a snapshot...
AFAICT VACUUM had better not ever need a snapshot because its xmin isn't
included in other vacuum commands' globalxmin so there's no guarantee that if
it had a snapshot that the tuples visible in that snapshot wouldn't disappear
out from
"Zoltan Boszormenyi" <[EMAIL PROTECTED]> writes:
> Zoltan Boszormenyi írta:
>> Gregory Stark írta:
>>> 4) Your problems with tsearch and timestamp etc raise an interesting
>>> problem.
>>>We don't need to mark this in pg_control because
g I've been wanting to do for a while and
basically the same approach I would have taken. It seems sound to me.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
d correct every time and now
> because of the passbyval nature of int8, the !AggState version is not slower
> than using the pointer directly.
Does this mean count() and sum() are slower on a 32-bit machine?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get train
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> There's no way the other transaction's timeout could fire while we're doing
> this is there? Are we still holding the lw locks at this point which would
> prevent that?
Ah, reading the patch I see comments in
at. As the patch stands, every query involved
> in the deadlock will be reported, which might be undesirable. We could
> make the test use the outermost session user's ID instead of current
> ID, but that might only move the security risks someplace else.
> Thoughts?
Perhaps
ind a few
backreferences.
I'll try some tests and see.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
utside of CVS in this case we perhaps suffered from
the opposite problem. The patch was fairly heavily tested on this end before
it was posted and I'm not sure those tests have been repeated since the merge.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Kind of verbose but nice that it's the same syntax as constraints.
Not sure how easy it would be to shoehorn into t he like processing, I could
look at that if you want.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Re
ray(select (1+random()*100)::integer from generate_series(1,100)));
bitmap-preread-v8.diff.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's 24x7 Postgres support!
---
"Gregory Stark" <[EMAIL PROTECTED]> writes:
> Aside from some autoconf tests and the documentation for the GUC I
> think it's all in there.
I'm sorry, it seems I accidentally grabbed an old tree to generate this patch.
I'll send along a better more recen
int32 n = PG_GETARG_INT32(0);
int32 lobound = PG_GETARG_INT32(1);
int32 hibound = PG_GETARG_INT32(2);
Datum *elems = palloc(sizeof(Datum) * n);
ArrayType *retval;
int i;
for (i=0; i
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about Ent
lan. Or somehow to
check whether it wouldn't be faster to just inline the memoized node directly
because perhaps there's a path available which would work for this read of it.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-De
skew, plus page headers, and
every record will have a different system data such as xmin for one.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL
training!
---(end of broadcast)---
TIP 6: explain analyze is your friend
exempt free software from any crypto export licenses.
Doesn't stop some other country from coming up with the same idea of course
but we don't generally worry about what laws some hypothetical country might
introduce at some point in the future. That way lies madness.
--
Gregory Sta
has any opportunity to substitute its result for the original
in prosrc. That might be interesting for other applications like compiled
languages, though I think they would still want to save the source in prosrc
and the bytecode in probin.
--
Gregory Stark
EnterpriseDB http://www.en
at is advantage?
It wouldn't require any core changes. It would be just another PL language to
load which can be installed like other ones. This could be a big advantage
because it doesn't look like there is a lot of support for putting th
obfuscation directly into the core
ass it to the normal plperl.
In such a scheme I think you would put the key in an attribute of the
language. Either in pg_lang or some configuration location which the
obfuscate:plperl interpreter knows where to find.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me abo
dump disable
>> sync scans so that it will reliably preserve row ordering. This is a
>> pretty trivial patch, but seeing how late we are in the 8.3 release
>> cycle, I thought I'd better post it for comment anyway.
>
> +1
I liked the "synchronized_sequential_sc
taking "with" as a reserved word.
I still hope to do recursive queries for 8.4 so I don't have strong feelings
for this part either way.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
-
e could use to make this decision instead
of the number of clauses? I would suggest the selectivity but from the sound
of it that's not going to help at all.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
--
ble
explain plan we could stuff a lot more data in there and have it be the UI's
responsibility to decide what data to display.
When that happens it would be nice to have the raw data used to generate the
cost estimations. At least the most important factors.
--
Gregory Stark
Enterpr
ainst a single-row table. The comments make me think you ran them but
just didn't show them though.
What about a merge join against an empty table? I suppose there would just be
no statistics?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about En
unevenly distributed then we need enough buckets to be able to
distinguish the dense areas from the sparse areas.
Perhaps something like starting with 1 bucket, splitting it into 2, seeing if
the distributions are similar in which case we stop. If not repeat for each
bucket.
--
Gregory Stark
ol = array[];
INSERT INTO foo (col) VALUES (array[]);
could be allowed if they could be contrived to introduce an assignment cast.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's RemoteDBA services!
---(end of broadc
artitions. Then let constraint_exclusion kick in to
narrow down which partitions should actually receive the updates and deletes.
I think triggers are the only solution for insert though.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB&#
es of data for both OLTP and
DSS systems.
I tend to be happier recommending triggers over rules if only because rules
are just harder to understand. Arguably they don't really work properly for
this use anyways given what happens if you use volatile functions like
random() in
"Joshua D. Drake" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>
>> A trigger will probably beat a rule for inserts/updates involving a small
>> number of rows.
>
> Which is exactly what partitioning is doing.
Say what?
--
Gregory Stark
Enterpris
Here's the WIP patch I described on -hackers to implemented "ordered" append
nodes.
merge-append-v1.diff.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's Slony
ict. On the other hand longer
fields take more space and take longer to compare so to make consistent use of
resources you would want to avoid storing and comparing large numbers of them
whereas you could afford much larger targets for small quick columns.
--
Gregory Stark
Ente
or other interfaces like it will run into
problems when the driver misinterprets the parameters.
> I think it would be a very bad idea
> to require that people use the function name in parameters,
I think were talking about only allowing it to disambiguate if the name is
shadowed by a
h to apply the patch from memory -- clearly not.
I assume the right thing happens if multiple deadlock check signals fire for
the same autovacuum?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
7;m not sure that's a case we really need to worry about.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail com
n't necessarily have the most up to date value
if it's been changed. But it's not something you're likely to change and you
can always adjust the environment variable manually to fix the problem.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
-
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> If I push the TOAST_TUPLES_PER_PAGE up to 16 I get another failure on the
>> same
>> line from trying to toast a sequence. If I add RELKIND_SEQUENCE to the
>> a
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> Testing Postgres with a small block size runs into an assertion failure when
>> it tries to toast a pg_proc tuple during initdb. I think the assertion is
>> just
>
template1 database in
/home/stark/src/local-HEAD/pgsql/src/test/regress/./tmp_check/data/base/1 ...
TRAP: FailedAssertion("!(rel->rd_rel->relkind == 'r')", File: "tuptoaster.c",
Line: 440)
--- tuptoaster.c13 Oct 2007 22:34:06 +0100 1.78
+++ tupt
Caught this in my testing with enhanced debugging checks.
Index: src/backend/access/heap/tuptoaster.c
===
RCS file:
/home/stark/src/REPOSITORY/pgsql/src/backend/access/heap/tuptoaster.c,v
retrieving revision 1.77
diff -u -r1.77
system but
don't want to block on any user-profiles which are locked by active users --
especially if you use database locks for user-visible operations which users
can drag out for long periods of time. (Not saying I agree with that design
but there are arguments for it and
files changed, 5 insertions(+), 364 modifications(!)
packed-varlena-efficiency_v0.patch.gz
Description: Binary data
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
====
RCS file:
/home/stark/src/REPOSITORY/pgsql/src/backend/tsearch/dict_thesaurus.c,v
retrieving revision 1.3
diff -c -r1.3 dict_thesaurus.c
*** src/backend/tsearch/dict_thesaurus.c25 Aug 2007 00:03:59 -
1.3
--- src/backend/tsearch/dict_thesaurus.c1
come in
from people who are more familiar with it than us. In my experience that's how
new maintainers for modules of free software are often found anyways.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Gregory Stark <[EMAIL PROTECTED]> writes:
>> "Tom Lane" <[EMAIL PROTECTED]> writes:
>>> This patch implements Florian's idea about how to manage snapshot xmax
>>> without the ugly and p
rdware but (aside from believing
the code will work of course) we should at a minimum be certain that the build
farm will detect the problem.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In versions
tid (and posid) should always be 4-byte aligned. So actually
it would never cross a hardware sector boundary.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 1: if posting/reading through
the line pointers in question to anything else. (because your
pin prevents the vacuum lock from coming in and trying to mark it unused).
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 9: In
prunes per update instead of a potentially unbounded number
of prunes.
This seems like a further optimization to think about after we have a place to
trigger the pruning where it'll do the most good.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---
> things to get bootstrap and prepared transactions to work, but on the
> whole it seems at least as clean as the code we have now. Comments?
Just that it will be fascinating to see what effects this has on the
benchmarks.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
"Pavan Deolasee" <[EMAIL PROTECTED]> writes:
> On 9/6/07, Gregory Stark <[EMAIL PROTECTED]> wrote:
>
>> Ah, as I understand it you can't actually do the pruning then because the
>> executor holds references to source tuple on the page. In other words
se the
executor holds references to source tuple on the page. In other words you can
never "get the vacuum lock" there because you already have the page pinned
yourself.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)--
Whether the index lookup should prune the heap chain is another issue.
Pruning chains is kind of the whole point of the exercise no?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at
http://www.postgresql.org/about/donate
too?
Or would it be too much extra overhead?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
outstanding
commands using early snapshots then subsequent planning ought to be able to
use the index. Even if outstanding commands are using old snapshots if we can
be sure they can't use the new plan then it would still be safe to use the
index in the new plan. Also in SERIALIZABLE mode those
ut CREATE INDEX, and
> worked up an updated README. Comments? Corrections?
You should also take the appendix to Heikki's README about CREATE INDEX that I
wrote.
>
> I plan to put this in src/backend/access/heap/README.HOT.
--
Gregory Stark
EnterpriseDB http://ww
h.
Index: src/backend/utils/sort/tuplesort.c
=======
RCS file: /home/stark/src/REPOSITORY/pgsql/src/backend/utils/sort/tuplesort.c,v
retrieving revision 1.77
diff -c -r1.77 tuplesort.c
*** src/backend/utils/sort/tuplesort.c 7 Jun 2007 19:19:57 - 1.77
--- src/backe
1 - 100 of 305 matches
Mail list logo
