Re: [HACKERS] What to do with inline warnings?

to mark unlikely branches (usually assertion failures) but I'm not sure how they work. And Gcc also has a few optimizations which are driven by profiling data but I it doesn't sound like this is one of them. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] What to do with inline warnings?

quite likely that the compiler is actually right (by chance) and we shouldn't be optimizing those cases at the expense of more common cases. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers

Re: [HACKERS] deadlock while doing VACUUM and DROP

that are out of your control :( -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] What in the world is happening on spoonbill?

, so this isn't an academic point. It might be a bit weird but pg_regress could stick a message in the output file before it does the comparison with the expected results. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about

Re: [HACKERS] 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: [HACKERS] 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: [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: [HACKERS] [PATCHES] WITH RECURSIVE patch V0.1

we could have a GUC variable which just allows the DBA to prohibit any recursive query without such a column and a fiter imposing a maximum value on it. That's probably the most appropriate option. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

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

Re: [HACKERS] idea: storing view source in system catalogs

had no way to replan any plans from a former definition of the view. Now that we have the query cache would we know that the view had changed and therefore the whole query needs to be replanned from source? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] Execution-time-sensitive timestamp regression tests

by midnight end -- 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 changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

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

seen on the page. or something like that. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Avoiding second heap scan in VACUUM

we're accumulating. It seemed safe enough when we had only one but I'm not sure what the consequences for this action are when there are several of them. Are we perhaps creating deadlocks? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS

Re: [HACKERS] BUG #4204: COPY to table with FK has memory leak

are done in bulk using a JOIN rather than one-at-a-time. Hm, it occurs to me that we could still do a join against the pending event trigger list... I wonder how feasible it would be to store the pending trigger event list in a temporary table instead of in ram. -- Gregory Stark EnterpriseDB

Re: [HACKERS] BUG #4204: COPY to table with FK has memory leak

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: This is expected to take lots of memory because each row-requiring-check generates an entry in the pending trigger event list. Hm, it occurs to me that we could still do a join

Re: [HACKERS] Avoiding second heap scan in VACUUM

vacuum. The trick is to know whether the last vacuum committed or not. If it didn't commit then it's not safe to remove those line pointers yet. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql

Re: [HACKERS] BUG #4204: COPY to table with FK has memory leak

to refer to bulk operations: Optimize referential integrity checks http://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php http://archives.postgresql.org/pgsql-hackers/2007-04/msg00744.php -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce

Re: [HACKERS] Overhauling GUCS

for example, good luck figuring out what to set it to. The vacuum cost delay factors are probably ripe for such a recast though. I think we need just one parameter vacuum_io_bandwidth or something like that. The bgwriter parameters might also be a candidate but I'm less certain. -- Gregory Stark

Re: [HACKERS] Overhauling GUCS

might exist. You also have no way to keep the file in a version control system or sync across servers etc. Have you *looked* at postgresql.conf.sample lately, Tom? It's a disaster. Maintenance is already difficult, and becoming more so as we add settings. What difficulties? -- Gregory Stark

Re: [HACKERS] synchronized scans for VACUUM

up very few vacuum cost delay points. Perhaps the vacuum cost delay for a cache hit ought to be 0? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Core team statement on replication in PostgreSQL

on re-finding index pointers :( -- 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

Re: [HACKERS] About dependency reports in DROP RESTRICT

if so it would be the DETAIL field? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] Overhauling GUCS

. That doesn't necessarily mean we have to ban users from touching the automatically generated config file or switch formats, but it relieves us of any responsibility for maintaining free-form text. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS

Re: [HACKERS] Overhauling GUCS

Andreas Pflug [EMAIL PROTECTED] writes: Gregory Stark wrote: Andreas Pflug [EMAIL PROTECTED] writes: Why do so many people here insist on editing postgresql.conf as primary means of changing config params? Isn't a psql -c SET foo=bar; MAKE PERSISTENT just as good as sed'ing

Re: [HACKERS] Overhauling GUCS

Andreas Pflug [EMAIL PROTECTED] writes: Gregory Stark wrote: So all you have is our existing file except with an additional layer of quoting to deal with, a useless SET keyword to annoy users, and a file that you need a bison parser Don't you think that's a little over the top, throwing

Re: [HACKERS] Overhauling GUCS

those who do use that feature *do* need to adjust those parameters because the server does *not* get them right automatically) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Overhauling GUCS

filename for such a file and include an include directive for it in the standard configuration file or you could just include instructions saying what include line to add to your config file in the installation instructions for your tool. Great, I'm glad we've resolved that issue. -- Gregory Stark

Re: [HACKERS] Overhauling GUCS

remains controversial; consider default value, per-session/runtime/restart, and enum lists as the list of things that are most needed there. Isn't that a list of what's *already* there? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS

Re: [HACKERS] math error or rounding problem Money type

. -- 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 changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Overhauling GUCS

statistic tables hurt planning time. The flip side of seeing how much larger tables help planning accuracy is much harder to measure. Offhand I don't see any systematic way to go about it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS

Re: [HACKERS] Overhauling GUCS

in a nearly constant sized data structure). -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] pg_dump restore time and Foreign Keys

it for the existing data at some later date. (Or even never) -- 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

Re: [HACKERS] Overhauling GUCS

Hakan Kocaman [EMAIL PROTECTED] writes: On 6/9/08, Gregory Stark [EMAIL PROTECTED] wrote: n_distinct. For that Josh is right, we *would* need a sample size proportional to the whole data set which would practically require us to scan the whole table (and have a technique for summarizing

Re: [HACKERS] Core team statement on replication in PostgreSQL

the rest. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Overhauling GUCS

. Also, we seem to be getting pretty far away from the original GUC discussion. Thank heavens :) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] Proposal - improve eqsel estimates by including histogram bucket numdistinct statistics

Zeugswetter Andreas OSB sIT [EMAIL PROTECTED] writes: I think for low ndistinct values we will want to know the exact value + counts and not a bin. So I think we will want additional stats rows that represent value 'a1' stats. Isn't that what our most frequent values list does? -- Gregory

Re: [HACKERS] Proposal - improve eqsel estimates by including histogram bucket numdistinct statistics

it produces. Somehow it could be informed of some holistic view of the quals on its children and how they're inter-dependent. If it's told that only one of its children will produce rows then it can use max() instead of sum() to calculate its rows estimate. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] Proposal - improve eqsel estimates by including histogram bucket numdistinct statistics

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: The screw case I've seen is when you have a large partitioned table where constraint_exclusion fails to exclude the irrelevant partitions. You're going to get 0 rows from all but the one partition which contains the 1

Re: [HACKERS] Proposal - improve eqsel estimates by including histogram bucket numdistinct statistics

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: It's possible that the second option I described -- teaching Append when to use something other than sum() -- would only work in the cases where constraint exclusion could be fixed though. In which case having

Re: [HACKERS] Proposal: Multiversion page api (inplace upgrade)

on performance grounds, but collation is not a property of the data at all. -- 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

Re: [HACKERS] .psqlrc output for \pset commands

the thing that struck me as odd was the messages appearing *before* the header. It seems to me the header should print followed by .psqlrc output followed by normal output. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support

Re: [HACKERS] Overhauling GUCS

could always steal more if we want or return some, as long as we're careful about when we do it. That would open the door to having these parameters be dynamically adjustable. That alone would be worthwhile even if we bypass all bells and whistles of the buffer manager. -- Gregory Stark

Re: [HACKERS] Overhauling GUCS

that even if we take this tact of making wal_buffers resizable by stealing buffers from the buffer manager for precisely the reasons Tom was describing. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers

Re: [HACKERS] Overhauling GUCS

is no longer a magic threshold for LIKE queries (in CVS HEAD) -- 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

Re: [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: [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-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Vacuuming leaked temp tables (once again)

log messages as soon as it sees such tables and start dropping them at some point later? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] interval madness ...

Hans-Juergen Schoenig [EMAIL PROTECTED] writes: why do i get a different timezone just because of adding one more century? i cannot see an obvious reason. What version of Postgres and what setting of TZ? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] interval madness ...

for the later commits but they weren't backpatched to 8.3 so unless you're using HEAD you won't get properly working timezones for post-2038 -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] TODO item: Allow data to be pulled directly from indexes

haven't been committed yet. As you seem to realize there has been a lot of discussion in this area already. The visibility map looks like a much more popular direction. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services

Re: [HACKERS] TODO item: Allow data to be pulled directly from indexes

not throw errors, for example). -- 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 changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [HACKERS] Git Repository for WITH RECURSIVE and others

, what makes you think one is more of a go-it-alone style of development than the other? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] WIP patch: reducing overhead for repeat de-TOASTing

for that case even if there's a further cache behind it for repeated fetches of out-of-line data. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Planned obsolescence in identify_system_timezone()

going to do it at all it should be once at startup (or config file read or some event like that). But I think I agree that it's just not our place at all and just defaulting to GMT is the right option. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] Bucket and batch

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

Re: [HACKERS] Explain XML patch

conflict with anything... but anyways...). -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] A new take on the foot-gun meme

tried selling them. Surely a movie counts as published!? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Please claim review items for commit fest!

for every item. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] [WIP] patch - Collation at database level

. Out of curiosity, what is a user-defined collation? Are there SQL statements to go around declaring what order code points should be sorted in? That seems like it would be... quite tedious! -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony

Re: [HACKERS] WIP patch: reducing overhead for repeat de-TOASTing

I'm inclined to think that we'd better turn that off by default, since it's not looking like it's catching anything new. Well at least it caught the bug that Mark was performance testing with a --enable-cassert build :/ -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [HACKERS] Resolving polymorphic functions with relateddatatypes

think the way it works now is weird too, but it's been that way forever and changing it would be a pretty massive behaviour change. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Switching between terminals

pg_sleep(10) between the two queries in the first file you run so that it hasn't updated both tables and exited before the second one even starts. But I'm just guessing since you haven't sent the actual files you're running. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [HACKERS] the un-vacuumable table

. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [HACKERS] PATCH: CITEXT 2.0

collation. That is, does this hash agree with your citext_eq on strings like foo bar = foobar and fooß = fooss ? You may have to use strxfrm -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list

Re: [HACKERS] PATCH: CITEXT 2.0

David E. Wheeler [EMAIL PROTECTED] writes: do I need to worry about memory leaks in citext_eq, citext_ne, citext_gt, etc., yes -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list

Re: [HACKERS] PATCH: CITEXT 2.0

in a Turkish locale which found certain sequences of characters to be insignificant for ordering. Someone who's using a citext data type has obviously decided that's precisely the kind of behaviour they want. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] CommitFest rules

that -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Identifier case folding notes

the only point of fiddling with this. Breaking this would take as further from spec-compliance than we are today. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Identifier case folding notes

there are other circumstances where this can arise select FOO from (select col as foo from bar) Not to mention temporary objects which are created and dropped inside functions. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support

Re: [HACKERS] No answers on CommitFest procedures?

are not so relevant as just whether we like the idea at all. -- 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

Re: [HACKERS] Auto-explain patch

between tracing and logging like log_explain_plan and so on. Perhaps we should keep the word trace for a more in-detail facility. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] WITH RECURSIVE updated to CVS TIP

submitters trees with just the patches they're missing (ie, skipping the patches they submitted upstream or merging them cleanly) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql

Re: [HACKERS] UUID - Data type inefficient

to the Postgres datatype. The rest of it seems to be pretty mysql-specific. Some of the problems are universal such as making index inserts especially random and making clustering impossible, but how much they hurt on different databases is going to be very different. -- Gregory Stark EnterpriseDB

Re: [HACKERS] Protocol 3, Execute, maxrows to return, impact?

the programmer will be sad. Back when I was doing PHP programming and I discovered that PHP's Postgres driver didn't support this I thought it was an outrageous bug. (It didn't help that the behaviour was to misbehave randomly rather than throw a meaningful error.) -- Gregory Stark EnterpriseDB

Re: [HACKERS] Protocol 3, Execute, maxrows to return, impact?

anyone's actually done any experiments to optimize libpq or other drivers to stream data efficiently, so I'm not sure how much you would really lose in practice today. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning

[HACKERS] Should SPI_gettypeid be extended to support returning the typmod?

as well? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] posix advises ...

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

Re: [HACKERS] [PATCHES] VACUUM Improvements - WIP Patch

vacuum's work-load. What we're doing now is kind of backwards. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

Re: [HACKERS] [PATCHES] VACUUM Improvements - WIP Patch

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: I like the idea of only having to do a single pass through the table though. Well, that argument was already overstated: we're not re-reading all of the table now. Just the pages containing dead line pointers

Re: [HACKERS] Fwd: Proposal - UUID data type

? SMTP? NTP? It tends to be important for network protocols since there's no gain in having non-interoperable protocols. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] [PATCH]-hash index improving

. The extra work on insert time is O(nlogn) amortized, but I'm not sure good amortized performance is good enough for Postgres. Users are unhappy when they're average performance is good but 1/1000 inserts thrashes their i/o rewriting the whole index... -- Gregory Stark EnterpriseDB http

Re: [HACKERS] [PATCH]-hash index improving

Heikki Linnakangas [EMAIL PROTECTED] writes: Gregory Stark wrote: For i/o-bound databases with very large indexes there should be an opportunity where btree lookups are O(logn) and hash lookups can in theory be O(1). Ignoring the big-O complexity, if a hash index only stores a 32-bit hash

Re: [HACKERS] Postgres-R: primary key patches

to the server that really, it only needs any UNIQUE NOT NULL combination of columns to match. Once the server has any such combination which matches it can skip checking the rest. I can't think of any way to write such a query in SQL. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] overlaps performance

Grzegorz Jaśkiewicz [EMAIL PROTECTED] writes: So my question would be, why isn't postgresql using indexes for OVERLAPS, and why optimizer doesn't substitute it with something like: (c = a AND d a) OR ( c = a AND c b) How would you use an index for that? -- Gregory Stark EnterpriseDB

Re: [HACKERS] overlaps performance

might still be lower. I think the reason we don't (aside from it not being at all useful in he past) is that it would lead to a lot of possible index scans being considered. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication

Re: [HACKERS] Do we really want to migrate plproxy and citext into PG core distribution?

by offloading development outside of core but provide users with a perceived complete system. For perl this is important because they want programmers to be able to assume certain modules are present. For postgres the case is less compelling since there isn't an interoperability issue. -- Gregory

Re: [HACKERS] Do we really want to migrate plproxy and citext into PG core distribution?

Dave Page [EMAIL PROTECTED] writes: On Tue, Jul 22, 2008 at 2:39 PM, Gregory Stark [EMAIL PROTECTED] wrote: Tom Lane [EMAIL PROTECTED] writes: From a project-management point of view, it's insanity to set a presumption that pgfoundry is just a proving ground for code that should eventually

Re: [HACKERS] [RFC] Unsigned integer support.

be a pretty massive semantics change. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] [RFC] Unsigned integer support.

explicit type casts. STATEMENT: select '100' + '100'; Perhaps we could kill two birds with one stone... -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] Research/Implementation of Nested Loop Join optimization

Manoel Henrique [EMAIL PROTECTED] writes: Yes, I'm relying on the assumption that backwards scan has the same cost as forward scan, why shouldn't it? Because hard drives only spin one direction -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] Adding WHERE clause to pg_dump

seems like the right option to me. The tricky bit would be how to deal with cases where you want a different where clause for different tables. But even if it doesn't handle all cases that doesn't mean a partial solution is unreasonable. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] Research/Implementation of Nested Loop Join optimization

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Manoel Henrique [EMAIL PROTECTED] writes: Yes, I'm relying on the assumption that backwards scan has the same cost as forward scan, why shouldn't it? Because hard drives only spin one direction Good joke

Re: [HACKERS] WITH RECUSIVE patches 0723

queries. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] WITH RECUSIVE patches 0723

that this is more common than the converse. I think if we have a choice between always materializing and always inlining then always materializing is much better. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via

Re: [HACKERS] [RFC] Unsigned integer support.

rules). -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] [WIP] patch - Collation at database level

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

Re: [HACKERS] Python 2.5 vs the buildfarm

it was released. But if you're happy doing the work I can't see any reason to stop you either. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] Type Categories for User-Defined Types

, but not because we wouldn't want to create new ones. Just because there isn't really any other meta data we want to store about type categories. Aside from the preferred type and the members there isn't anything more to say about them. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] Should creating a new base type require superuser status?

to create a preferred type? -- 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

Re: [HACKERS] Should creating a new base type require superuser status?

new semantics. Unless you're going to allow them to create new C functions, I'm not clear on how much they're going to be able to change the semantics. Well there's plenty that can be done just using text or bytea as representations. citext, or uuid for example. -- Gregory Stark

<    4   5   6   7   8   9   10   11   12   13   >