Re: [PATCHES] WIP Join Removal

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 company_id,customer_id and then using an index to look them up in invoices. -- Gregory Stark

Re: [PATCHES] WIP Join Removal

be duplicate values of pk in b. c) Turn bad mysqlish queries which are really semijoins (used to work around their historic lack of subqueries) such as: SELECT DISTINCT a.pk FROM a JOIN b USING (x) into SELECT a.pk FROM a WHERE x IN (SELECT x FROM b) -- Gregory Stark EnterpriseDB

Re: [PATCHES] Explain XML patch v2

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.postgresql.org/wiki/CommitFest:2008-07 so any

Re: [PATCHES] [HACKERS] Hint Bits and Write I/O

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. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] [HACKERS] Hint Bits and Write I/O

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 PostgreSQL training! -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make

Re: [PATCHES] Feature: give pg_dump a WHERE clause expression

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 pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes

Re: [PATCHES] \d+ should display the storage options for columns

: ! ???, ! false); ! printTableAddCell(cont, PQgetvalue(res, i, 6), false); ! } } /* Make footers */ -- Gregory Stark

Re: [HACKERS] [PATCHES] WITH RECURSIVE patch V0.1

code ) statement_timeout becomes much less useful. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http

[PATCHES] \d+ should display the storage options for columns

cells[i * cols + cols - 1] = mbvalidate(PQgetvalue(res, i, 5), myopt.encoding); #else cells[i * cols + cols - 1] = PQgetvalue(res, i, 5); #endif + } } /* Make title */ -- Gregory Stark EnterpriseDB http

Re: [PATCHES] \d+ should display the storage options for columns

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 thing to add to \d+ Sorry, sent the wrong

Re: [PATCHES] [HACKERS] WITH RECURSIVE patch V0.1

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, well, ick. -- Gregory Stark EnterpriseDB

Re: [PATCHES] WITH RECURSIVE patch V0.1

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: # with recursive x(level, parent, child) as ( select 1::integer, * from

Re: [PATCHES] WITH RECURSIVE patch V0.1

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 the data contains no loops but the database doesn't. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask

Re: [PATCHES] Patch to change psql default banner v6

. 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 synonym for \? not come up? Or has it been rejected? It seems simplest. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] create or replace language

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 some reason. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get

Re: [PATCHES] [HACKERS] Proposed patch - psql wraps at window width

it aligned:autowrap instead of just wrap? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [PATCHES] [HACKERS] Proposed patch - psql wraps at window width

format aligned:autowrap I suppose. It seems kind of inconvenient though, what advantage does it have? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org

Re: [PATCHES] float4/float8/int64 passed by value with tsearchfixup

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 Production Tuning -- Sent via pgsql-patches mailing

Re: [PATCHES] Proposed patch - psql wraps at window width

, 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 the terminal line length is between 66 and 80 characters. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [PATCHES] Proposed patch - psql wraps at window width

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 Ask me about EnterpriseDB's PostGIS

Re: [PATCHES] float4/float8/int64 passed by value with tsearchfixup

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-patches mailing list (pgsql-patches@postgresql.org) To make changes to your subscription

Re: [PATCHES] Proposed patch - psql wraps at window width

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 that case, imho it should just default to 80 columns if COLUMNS is unset. -- Gregory Stark EnterpriseDB

Re: [PATCHES] Proposed patch - psql wraps at window width

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 columns if COLUMNS is unset. It would be a spectacularly awful

Re: [PATCHES] Improve shutdown during online backup

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 EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS

Re: [PATCHES] datum passed to macro which expects a pointer

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 pass-by-value. Seems unlikely to be a net win though. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] EXPLAIN progress info

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 its children report and its actual and expected rows and its

Re: [PATCHES] EXPLAIN progress info

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: a) the overhead of counting rows and loops is there for every query execution, even if you

Re: [PATCHES] Indexam API changes

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 because they would have to solve X first. -- Gregory Stark

Re: [PATCHES] Partial match in GIN

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 behaviour is identical just register the same function twice. -- Gregory Stark

[PATCHES] EXPLAIN progress info

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 EnterpriseDB's PostGIS support

Re: [PATCHES] EXPLAIN progress info

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/pgsql-general/2008-04/msg00402.php Seems like pg_relation_size

Re: [PATCHES] Expose checkpoint start/finish times into SQL.

and has to be checked against the WAL logs. -- 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

Re: [PATCHES] psql command aliases support

delivered by the parser are substituted, illustrated here with your example: To be more explicit what I meant was someone doing #= \alias old select version(); ... #= \oldd oops #= \old #= select 'where is all my output going?' #= select 'what happened to my ldd file?' -- Gregory Stark

Re: [PATCHES] psql command aliases support

. -- 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

Re: [PATCHES] psql command aliases support

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 different command entirely. Unsurprisingly it's going to do something

Re: [PATCHES] psql command aliases support

before backing ourselves into a corner. I can't imagine much of a use case for being able to alias backslash commands themselves. They're already ridiculously terse anyways. How many keystrokes can you possibly save? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me

Re: [PATCHES] Consistent \d commands in psql

to play it safe and have \dT macaddr show the user that there are now two matching data types. So I guess I should just play along and pretend that's what I meant all along :) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support

Re: [PATCHES] Consistent \d commands in psql

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 having \dfU and \dfS too I suppose, though I doubt most people would find them. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] Consistent \d commands in psql

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 for example. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask

Re: [PATCHES] Consistent \d commands in psql

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 rtrim for example. Interesting idea. IIUC, \df would give

Re: [PATCHES] Consistent \d commands in psql

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_ the system and user function and make it easier to see the conflict

Re: [PATCHES] int8/float8/time/timestamp[tz]/float4 passed by value, was Re: Fix HAVE_LONG[_LONG]_INT_64 to really define to 1

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 trained by Bruce Momjian - ask me about

Re: [PATCHES] int8/float8/time/timestamp[tz]/float4 passed by value, was Re: Fix HAVE_LONG[_LONG]_INT_64 to really define to 1

. -- 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

Re: [PATCHES] Re: int8/float8/time/timestamp[tz]/float4 passed by value, was Re: Fix HAVE_LONG[_LONG]_INT_64 to really define to 1

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 it's a purely a run-time issue and doesn't affect on-disk storage

Re: [PATCHES] Logging conflicted queries on deadlocks

the outermost session user's ID instead of current ID, but that might only move the security risks someplace else. Thoughts? Perhaps we should only do this if the current user's ID is the same as the outermost session user's ID? -- Gregory Stark EnterpriseDB http

Re: [PATCHES] Logging conflicted queries on deadlocks

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 indicating that yes that's possible and no, we

Re: [PATCHES] Proposed patch for 8.3 VACUUM FULL crash

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 Ask me about EnterpriseDB's 24x7 Postgres support

Re: [PATCHES] Proposed patch for bug #3921

. 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 RemoteDBA services! ---(end of broadcast

Re: [PATCHES] Bitmap index scan preread using posix_fadvise

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 recent version. Argh. -- Gregory Stark

Re: [PATCHES] Bitmap index scan preread using posix_fadvise

()*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! ---(end of broadcast

Re: [PATCHES] [8.4] Updated WITH clause patch (non-recursive)

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-Demand Production Tuning ---(end of broadcast)--- TIP 7: You can help support

[PATCHES] Bitmap index scan preread using posix_fadvise (Was: There's random access and then there's random access)

= construct_array(elems, n, INT4OID, 4, true, 'i'); PG_RETURN_ARRAYTYPE_P(retval); } -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! ---(end of broadcast)--- TIP 7: You can help

Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

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

Re: [PATCHES] WIP: plpgsql source code obfuscation

. 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 code. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask

Re: [PATCHES] WIP: plpgsql source code obfuscation

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.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training

Re: [PATCHES] WIP: plpgsql source code obfuscation

. 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 about EnterpriseDB's

Re: [PATCHES] WIP: plpgsql source code obfuscation

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 Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [PATCHES] [8.4] Updated WITH clause patch (non-recursive)

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 ---(end of broadcast)--- TIP 3: Have you checked our

Re: [PATCHES] Proposed patch: synchronized_scanning GUC variable

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_scans idea myself. But otherwise, sure. -- Gregory Stark EnterpriseDB http

Re: [PATCHES] [HACKERS] OUTER JOIN performance regression remains in 8.3beta4

of it that's not going to help at all. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! ---(end of broadcast)--- TIP 4: Have you searched our list archives? http

Re: [PATCHES] Proposed patch to make mergejoin cost estimation more symmetric

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 EnterpriseDB's 24x7 Postgres support

Re: [PATCHES] Proposed patch to make mergejoin cost estimationmore symmetric

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 EnterpriseDB http://www.enterprisedb.com Ask me

Re: [PATCHES] Better default_statistics_target

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 EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [PATCHES] [GENERAL] Empty arrays with 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 broadcast)--- TIP 4: Have you

Re: [PATCHES] [DOCS] Partition: use triggers instead of rules

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 EnterpriseDB http://www.enterprisedb.com Ask me

Re: [PATCHES] [DOCS] Partition: use triggers instead of rules

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 your where clause. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask

Re: [PATCHES] [DOCS] Partition: use triggers instead of rules

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's 24x7 Postgres support! ---(end of broadcast

[PATCHES] Ordered Append WIP patch v1

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 Replication support! ---(end

Re: [PATCHES] Better default_statistics_target

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 EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] V0.2 patch for TODO Item: SQL-language referenceparameters by name.

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 variable in an inner scope. -- Gregory Stark EnterpriseDB

Re: [PATCHES] Autovacuum cancellation

if multiple deadlock check signals fire for the same autovacuum? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe

Re: [PATCHES] Autovacuum cancellation

already fired its deadlock check before it was waiting directly on autovacuum. But the only way I can see it happening is if another process is cancelled before its deadlock check fires and the signals are processed out of order. I'm not sure that's a case we really need to worry about. -- Gregory

Re: [PATCHES] Win32: Minimising desktop heap usage

likely to change and you can always adjust the environment variable manually to fix the problem. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives

Re: [PATCHES] Assertion failure with small block sizes

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 assertion then it passes all regression tests even if I push

[PATCHES] Assertion failure with small block sizes

-rd_rel-relkind == RELKIND_UNCATALOGED); /* * Get the tuple descriptor and break down the tuple(s) into fields. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9

Re: [PATCHES] Assertion failure with small block sizes

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 wrong and RELKIND_UNCATALOGUED is valid here. Uh, what

[PATCHES] Packed varlena tuptoaster.c oops

; - toast_sizes[i] = VARSIZE(toast_values[i]); need_change = true; need_free = true; -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 7: You can help support

Re: [PATCHES] [HACKERS] 'Waiting on lock'

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 people do do it) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

[PATCHES] Eliminate more detoast copies for packed varlenas

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

Re: [PATCHES] [COMMITTERS] pgsql: Avoid possibly-unportable initializer, per buildfarm warning.

, sizeof(TheLexeme), cmpLexemeQ); if (res == NULL) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 5: don't forget to increase your free space map settings

Re: [PATCHES] PL/TCL Patch to prevent postgres from becoming multithreaded

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

Re: [PATCHES] HOT patch - version 15

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 Usenet, please send an appropriate subscribe

Re: [PATCHES] Yet more tsearch refactoring

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 below 8.0, the planner

Re: [PATCHES] WIP patch for latestCompletedXid method of computing snapshot xmax

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 performance-losing tactic of taking XidGenLock and ProcArrayLock at the same time. I had

Re: [PATCHES] HOT patch - version 15

it unused). -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do

Re: [PATCHES] WIP patch for latestCompletedXid method of computing snapshot xmax

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 ---(end of broadcast

Re: [PATCHES] HOT patch - version 15

. It seems an index lookup tries to prune a heap chain, and he was asking if it should look at other chains on the page; I said not. 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

Re: [PATCHES] HOT patch - version 15

already have the page pinned yourself. -- 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

Re: [PATCHES] HOT documentation README

? 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://www.enterprisedb.com ---(end of broadcast

Re: [PATCHES] HOT documentation README

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 same statements hold for temporary tables. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] HOT documentation README

? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org

[PATCHES] Buglet in Sort Method explain output in degenerate case

); + state-boundUsed = true; state-status = TSS_BOUNDED; } @@ -2284,7 +2285,6 @@ REVERSEDIRECTION(state); state-status = TSS_SORTEDINMEM; - state-boundUsed = true; } /* -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [PATCHES] HOT patch - version 14

declaring that the tid might sometimes not change after an update. Not sure what this translates to for MaxHeapTuplesPerPage though. The rest I know less about and will leave to Pavan and Heikki (or anyone else who was following those details more closely). -- Gregory Stark EnterpriseDB

Re: [PATCHES] HOT patch - version 14

Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Pavan Deolasee [EMAIL PROTECTED] writes: Please see the version 14 of HOT patch attached. I expected to find either a large new README, or some pretty substantial additions to existing README files, to document how

Re: [PATCHES] HOT patch - version 14

. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

Re: [PATCHES] tsearch core path, v0.58

would like to see all the data types in a file in adt. Even if it's just a single file containing mostly just glue functions into code in sc/backend/tsearch. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast

Re: [PATCHES] Repair cosmetic damage (done by pg_indent?)

Decibel! [EMAIL PROTECTED] writes: On Sun, Jul 29, 2007 at 12:06:50PM +0100, Gregory Stark wrote: You would have to recompile with the value at line 214 of src/backend/utils/adt/pg_lzcompress.c set to a lower value. Doesn't seem to be working for me, even in the case of a table with a bunch

Re: [PATCHES] Repair cosmetic damage (done by pg_indent?)

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: The scenario I was describing was having, for example, 20 fields each of which are char(100) and store 'x' (which are padded with 99 spaces). So the row is 2k but the fields are highly compressible, but shorter than

Re: [PATCHES] Repair cosmetic damage (done by pg_indent?)

effective. They require a static dictionary but then that's precisely what I'm thinking of. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [PATCHES] Correction of how to use TimeZone by ControlFile(xlog.c)

the timestamps in the appropriate timezone for user's consumption. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

  1   2   3   >