Re: [HACKERS] Synchronous Log Shipping Replication

most of them come from though? -- 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:

Re: [HACKERS] Transaction Snapshots and Hot Standby

t in the WAL. The slave then keeps a copy of the last snapshot it saw in the WAL and any new query which starts up uses that. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsq

Re: [HACKERS] Transaction Snapshots and Hot Standby

when you take action it fixes the problem immediately as WAL reply can recommence which seems like a better deal than a bloated database. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-

Re: [HACKERS] Postgresql coding conventions

es of this where there aren't exceptions. I don't like the idea of a massive cleanup patch for this but if someone's doing major surgery on a module it could be worth fixing up names in that module to be consistent at the same time. -- Gregory Stark EnterpriseDB http:

Re: [HACKERS] Our CLUSTER implementation is pessimal

Tom Lane <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> Yeah, I've been thinking about how to use the planner to do this. > > I thought the answer to that was going to be more or less "call > cost_sort() and cost_index() and c

Re: [HACKERS] Common Table Expressions (WITH RECURSIVE) patch

uot;. If it doesn't define those terms then it's definitely different from what I read. If it does, read on to see what it does with them. The main reason to define them appeared to be to use them to say that supporting mutual recursion is not required. -- Gregory Stark EnterpriseDB

Re: [HACKERS] [PATCH] Cleanup of GUC units code

Tom Lane <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> Alvaro Herrera <[EMAIL PROTECTED]> writes: >>> It's good as a joke, but what if the user says '1024b'? Does it mean >>> 1024 blocks or one kilobyte?

Re: [HACKERS] [PATCH] Cleanup of GUC units code

posix-style "blocks" relevant?! -- 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] [PATCH] Cleanup of GUC units code

quot;1g" > > Perhaps this would be a great place for a HINT listing all > valid inputs, if not there already? It is, I paraphrased it on my original message as: HINT: It's perfectly clear what you want but I'm going to refuse to do it until you type it exactly as I sa

Re: [HACKERS] [PATCH] Cleanup of GUC units code

of Postgres server and docs (no relaxation at all there) I believe we're already fairly stringent about this as we should be. > * in the longer term, we look for the solution to be a config checker I don't think a config checker directly addresses the same problem. I never set work_

Re: [HACKERS] Our CLUSTER implementation is pessimal

e we'll have to deform it, and reform it using the new tuple descriptor and just the columns excluding the header and pass that to the heap rewrite module. Passing the header separately. Heap rewrite would have to call HTSV on just the header (with the same hack I put in for this pa

Re: [HACKERS] Proposed patch: make pg_dump --data-only consider FK constraints

disabling or dropping the constraints and then have a hint to indicate how to do that with Postgres. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@po

Re: [HACKERS] About that CommitFest redirect page ...

ctive commitfest to the currently open commitfest which makes it clear when to use which. -- 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

Re: [HACKERS] Prototype: In-place upgrade v02

anything inside relation files, so no scanning of > relations is required because of that. Neither will the FSM rewrite. Not sure > about DSM yet. And just to confirm -- they don't change the name of the files the postmaster expects to find in its data directory, right? -- Gregory

Re: [HACKERS] code coverage patch

no tuplesorts are spilling to disk, no coverage of mark/restore on index scans... -- 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] Patch: propose to include 3 new functions into intarray and intagg

Markus Wanner <[EMAIL PROTECTED]> writes: > Hi, > > Gregory Stark wrote: >> Regarding the patch listed on the commitfest "3 new functions into intarray >> and intagg" (which I just noticed has a reviewer listed -- doh): > > ..well, just add your name as

Re: [HACKERS] Patch: propose to include 3 new functions into intarray and intagg

thing seem like they might be useful functionality. but I have a feeling others might feel differently. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql-hac

Re: [HACKERS] Page layout footprint

meone is surely going to find some counter-example) Doesn't really change the argument though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresq

Re: [HACKERS] Question regarding the database page layout.

Tom Lane <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> Tom Lane <[EMAIL PROTECTED]> writes: >>> BTW, there are at least two copies of that code to be changed. I'd >>> suggest grepping for assignments to t_hoff to be

Re: [HACKERS] Question regarding the database page layout.

Tom Lane <[EMAIL PROTECTED]> writes: > BTW, there are at least two copies of that code to be changed. I'd > suggest grepping for assignments to t_hoff to be sure there aren't more. I did send in a patch a while ago to get rid of the old HeapFormTuple() and friends

Re: [HACKERS] Index scan troubles

ur equality case which is effectively x=const, y=const, z=const. It's not for row comparisons case for which you need a funny "header" ScanKey. See the comments in access/skey.h, search for "row comparisons". I'm not sure if there's a function to create this f

Re: [HACKERS] Question regarding the database page layout.

"Ryan Bradetich" <[EMAIL PROTECTED]> writes: > Hello Greg, > > On Tue, Sep 2, 2008 at 8:30 AM, Gregory Stark <[EMAIL PROTECTED]> wrote: >> >> But I'm confused. You seem to be tweaking the alignment of the data inside >> the >> tupl

Re: [HACKERS] WIP patch: Collation support

ot sure if that's a "nobody really cares" issue or a bug we should aim to fix with real collation support. -- 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] Question regarding the database page layout.

benefit unless the > code that inserts tuples into disk pages knows to do something different in > the int-align case. +1 -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Question regarding the database page layout.

tmap is 2-5 bytes (mod 8) long. I thought the goal was to save space by aligning the tuples on the page more densely. That seems to me to be more fruitful as about half the tuples will save four bytes even on tables with small or missing null bitmaps. -- Gregory Stark EnterpriseDB

Re: [HACKERS] [PATCH] Cleanup of GUC units code

here you had to specify some things in units of Postgres blocks, for example. -- 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 su

Re: [HACKERS] [PATCH] Cleanup of GUC units code

g MB and Mb > to > mean the same thing is insane. Because you think some user will be trying to specify their shared_buffers in bits? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-

Re: [HACKERS] Window functions patch v04 for the September commit fest

;t actually have any ideas of how to deal with that one :( -- 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

[HACKERS] Our CLUSTER implementation is pessimal

rceUnique, int workMem, bool randomAccess); *** *** 69,74 --- 72,78 extern void tuplesort_puttupleslot(Tuplesortstate *state, TupleTableSlot *slot); + extern void tuplesort_putrawtuple(Tuplesortstate *state, HeapTuple tup); extern void tuplesort_putind

Re: [HACKERS] Attaching error cursor position to invalid constant values

lect 'foo'+0, 'foo'+0.0; and when you get the error the you would have to deduce which constant is in error based on the type it describes. That could be quite a bit more complex than this example. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get

Re: [HACKERS] Attaching error cursor position to invalid constant values

t it or position the cursor. Perhaps there could be a psql option to control whether to show the error position and perhaps that setting could be based on the length of the query or how many lines are in it but that seems unnecessarily baroque. It doesn't seem outrageously chatty to me. Bette

Re: [HACKERS] Proposal: new border setting in psql

should prove a rest_escape() function for that purpose. I wonder if it's worth keeping two variants at all really. Why not just make psql's native table formatting exactly ReST? Is there any part of it that we don't like as much as our existing tables? -- Gregory Stark Enterpr

Re: [HACKERS] New FSM allocation policy

ft branch if it's > target and has enough free space else take right branch if there's enough free space else take left branch). -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via p

Re: [HACKERS] September Commit Fest coming soon!

entary on specific questions about that specific snapshot. However when a committer is actually looking to commit the code he'll want to be sure he has the most recent snapshot including any later changes that might not have warranted an email. -- Gregory Stark EnterpriseDB http:

Re: [HACKERS] code coverage patch

shared object link rules don't use CFLAGS. Shared object link rules should use another variable (LDFLAGS?) and those options should be added that variable as well. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB

Re: [HACKERS] Implementing cost limit/delays for insert/delete/update/select

"Tom Lane" <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> You would have to test for whether it's time to sleep much more often. >> Possibly before every ExecProcNode call would be enough. > > That would have overhead c

Re: [HACKERS] Implementing cost limit/delays for insert/delete/update/select

a. You would have to test for whether it's time to sleep much more often. Possibly before every ExecProcNode call would be enough. Even then you have to worry about the i/o and cpu resources used by by tuplesort. And there are degenerate cases where a single ExecProcNode could do a l

Re: [HACKERS] IN, BETWEEN, spec compliance, and odd operator names

>> clear what it is. > > How would the planner get the estimated costs associated to any operator > choice in this case? We don't need to evaluate costs until well after this point. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce

Re: [HACKERS] Extending error-location reports deeper into the system

on. The original objection included caveats that there may be other sites that have uncertainty about whether to include the line number. Are you sure there aren't any? Are you sure there isn't anywhere else lurking that expects equal to really mean equal? Perhaps someplace that builds

Re: [HACKERS] proposal sql: labeled function params

conflicts with named parameters, conflicts with operators, introduce an un-sqlish syntax and remove a feature users have already made use of and introduce backwards compatibility issues for those users? At any point in this discussion has anyone explained why these labels would actually be a good

[HACKERS] Volatile functions in subqueries don't prevent subqueries from being evaluated in initplans?

width=0) -> Seq Scan on x (cost=0.00..64.80 rows=3480 width=4) (4 rows) -- 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 su

[HACKERS] Is mdextend really safe?

f file. Is that true? -- 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:

Re: [HACKERS] Patch: plan invalidation vs stored procedures

s > not plan to fix that ? Now who's trolling :) -- 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 m

Re: [HACKERS] Overhauling GUCS

t, in your opinion, is "the main problem"? I'm not sure we agree on > that. The main problem that I've seen described is what I mentioned before: allowing adjusting the postgresql.conf GUC settings by remote users who don't have shell access. -- Gregory Stark EnterpriseDB

Re: [HACKERS] Overhauling GUCS

you and others make it less likely every time you throw up big insoluble problems like above though. As a consequence every proposal has started with big overly-complex solutions trying to solve all these incidental issues which never go anywhere instead of simple solutions which directly tackle the mai

Re: [HACKERS] SeqScan costs

"Tom Lane" <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >>> On Tue, 2008-08-12 at 15:46 -0400, Tom Lane wrote: >>>> This is only going to matter for a table of 1 block (or at least very >>>> few blocks)

Re: [HACKERS] any psql static binary for iphone ?

I haven't looked at it but there's this: http://www.postgresql.org/about/news.988 -- 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] proposal sql: labeled function params

eems like a ridiculous idea. It's a fancy way of passing an extra parameter to the function intended to be used for a particular "label" purpose. Your xml function could just as easily take two functions f(name,value) instead of using a special spelling for ",". That it i

Re: [HACKERS] Join Removal/ Vertical Partitioning

ic, which is > quite interesting. I notice there is a blog there about join removal, > posted about 12 hours later than my original post. Seems to validate the > theory anyway. Our posts have a wider audience than may be apparent :-) Well turnabout's fair play...

Re: [HACKERS] gsoc, oprrest function for text search take 2

ell it doesn't really matter which type. If you store Datums which are already detoasted then the DatumGetTextP and DatumGetTextPP will just be noops anyways. If you store packed data (from DatumGetTextPP) then it's probably safer to store it as Datums so if you need to pass it to any f

Re: [HACKERS] SeqScan costs

till means up to 9 btree comparisons. Still less than 200 but it's not entirely free. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing list (pgsql-hackers@postg

Re: [HACKERS] Replay attack of query cancel

cancel key it automatically switches to new-style cancel messages. Or we could just bump the protocol version. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql-hack

Re: [HACKERS] SeqScan costs

consistently better cost estimates that would be a huge help. I've been running benchmarks where I see accurate random_page_costs of 13-80 on uncached data on a moderate sized raid array. But of course when a some of the data is cached the effective random_page_cost is much much lower than tha

[HACKERS] psql bug -- using old variables and database connection

the new connection */ if (!pset.quiet) -- 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 you

Re: [HACKERS] IN vs EXISTS equivalence

treated as > > EXISTS(a) > OR EXISTS(b) Kind of confused by what you mean here. Can you give an example? The usual transformation to consider with UNION is to transform SELECT ... WHERE x OR y into SELECT ... WHERE x UNION ALL SELECT ... WHERE y AND NOT x (modulo handling NULLs prope

[HACKERS] Skimming icc warnings on mongoose

ing #186: pointless comparison of unsigned integer with zero Assert(plen >= 0 && plen < mlen); -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-h

Re: [HACKERS] Proposal: PageLayout footprint

y does not > happen often but footprint should protect people to shot himself. My version of GCC doesn't have that option, what does it do? If structure members aren't in the order they're defined and padded to the alignment they're declared to have in pg_type then Postgres c

Re: [HACKERS] Question regarding the database page layout.

uple then heap_form_tuple needs to know where to put it so it ends up at right alignment. -- 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

Re: [HACKERS] patch: Add columns via CREATE OR REPLACE VIEW

SELECT * FROM b; What about this? CREATE OR REPLACE VIEW a AS (select 1 as b, 2 as c, 'three as a); SELECT * FROM b; -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsq

Re: [HACKERS] Visibility Groups

"Alvaro Herrera" <[EMAIL PROTECTED]> writes: > Gregory Stark wrote: > >> I think Simon's interface was overly complex but if we can simplify it then >> it >> could be useful. As Grittner mentioned implicit queries could make use of it >> automa

Re: [HACKERS] Visibility Groups

"Gregory Stark" <[EMAIL PROTECTED]> writes: > I think Simon's interface was overly complex but if we can simplify it then it > could be useful. As Grittner mentioned implicit queries could make use of it > automatically. Also pg_dump or Slony could make use of it a

Re: [HACKERS] Visibility Groups

with newer records a long-running transaction will prevent any of those old records from being vacuumed. -- 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] Visibility Groups

you'll need, then have a command to indicate you won't need any further objects beyond those. -- 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] DROP DATABASE always seeing database in use

"Russell Smith" <[EMAIL PROTECTED]> writes: > Gregory Stark wrote: >> It seems there's something wrong with CheckOtherDBBackends() but I haven't >> exactly figured out what. There are no other sessions but drop database keeps >> saying "re

Re: [HACKERS] Status of DISTINCT-by-hashing work

ehow it would be a great improvement even if we didn't actually improve the plans available. Any idea what would the needed executor infrastructure look like? Would it have anything in common with the OLAP window functions infrastructure? -- Gregory Stark EnterpriseDB ht

Re: [HACKERS] searching bison guru - grouping sets implementation

db.postgresql.devel.general/83578 (Oh look at that, he actually used precisely that phrase) -- 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] searching bison guru - grouping sets implementation

ady and noted the same conflict: http://article.gmane.org/gmane.comp.db.postgresql.devel.general/83563/match=rollup Tom pointed out that there's more than one way to skin a cat: http://thread.gmane.org/gmane.comp.db.postgresql.devel.cvs/22326/focus=83563 (Oh look at that, he actually used

Re: [HACKERS] Mini improvement: statement_cost_limit

be taking that long. I would be much more comfortable if it produced a warning, not an error. And much more if we implemented my previous thought of having some settings which generate warnings if they're set at startup saying that's not recommended. -- Gregory Stark EnterpriseDB

Re: [HACKERS] DROP DATABASE always seeing database in use

to > see why it isn't working. Michael Fuhr solved it so this is academic but, the buildfarm runs make installcheck? I thought it just ran make check -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent vi

Re: [HACKERS] DROP DATABASE always seeing database in use

"Michael Fuhr" <[EMAIL PROTECTED]> writes: > On Mon, Aug 04, 2008 at 11:51:35AM +0100, Gregory Stark wrote: >> It seems there's something wrong with CheckOtherDBBackends() but I haven't >> exactly figured out what. There are no other sessions but drop

[HACKERS] DROP DATABASE always seeing database in use

2008-08-04 11:46:45.619642+01 | 2008-08-04 11:46:45.620115+01 | 2008-08-04 11:45:19.827702+01 | | -1 (1 row) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mail

Re: [HACKERS] Mini improvement: statement_cost_limit

set enable_seqscan in an individual session but not in postgres.conf. Or perhaps again just print a warning that it's not recommended as a global configuration. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication suppor

Re: [HACKERS] Parsing of pg_hba.conf and authentication inconsistencies

could build a new set of structures and if there are any errors just throw them out before replacing the old ones. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-hackers mailing list (pgsql-hac

Re: [HACKERS] Parsing of pg_hba.conf and authentication inconsistencies

etending everything's ok. Perhaps authentication methods should have a function to check whether the method is supported which is called when the file is parsed. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via p

Re: [HACKERS] Messed up CVS status of two ECPG files

"Tom Lane" <[EMAIL PROTECTED]> writes: > Gregory Stark <[EMAIL PROTECTED]> writes: >> These two files seem to be getting updated every time I do a CVS update. > > Doesn't happen here --- maybe something odd in your local CVS state? Huh, indeed. I need

[HACKERS] Messed up CVS status of two ECPG files

s true then we should just cvs delete them. U src/interfaces/ecpg/preproc/keywords.c U src/interfaces/ecpg/test/expected/connect-test1.c -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-

Re: [HACKERS] Fixing the representation of ORDER BY/GROUP BY/DISTINCT

; Oid sortop; /* the ordering operator ('<' op), or 0 */ > boolnulls_first;/* do NULLs come before normal values? */ > } SortGroupClause; So ASC/DESC is represented by using > for sortop? -- Gregory Stark EnterpriseDB h

Re: [HACKERS] Fixing the representation of ORDER BY/GROUP BY/DISTINCT

#x27;s true. We could store the sort key in the hash along with the resulting tuple and replace the resulting tuple iff the new sort key is less than the old sort key. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication supp

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

es which used an existing set of input/output >> functions but defined 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 usi

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

rojan-horse vector for executing functions as some other > user. Would it be enough to only require super-user to create a preferred type? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via

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

n't necessarily want to define. I do agree that having SQL commands to create new type categories, even a new catalog table is overkill, 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. A

Re: [HACKERS] Python 2.5 vs the buildfarm

work with a new Redhat release, for example. We would just say 8.1 is only supported on those systems it was supported on when 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.enterpri

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

llations and the syntax to select a collation for each 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 c

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

and they often go out of their way to avoid them (causing themselves headaches when they then need to deal with casting rules). -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sen

Re: [HACKERS] WITH RECUSIVE patches 0723

we should advertise this as the approved way to disable subquery inlining. I would still suggest using OFFSET 0 for that. But I also don't agree with you that this is more common than the converse. I think if we have a choice between always materializing and always inlining then always materiali

Re: [HACKERS] WITH RECUSIVE patches 0723

to make recursive queries work? Once we have that we'll just use those executor nodes even for non-recursive queries. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql-ha

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 sc

Re: [HACKERS] Adding WHERE clause to pg_dump

s a table missing columns referenced in the where clause then fail with the appropriate error. Which 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 al

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

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

character 14 > HINT: Could not choose a best candidate operator. You might need to add > explicit type casts. > STATEMENT: select '100' + '100'; Perhaps we could kill two birds with one stone... -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

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

the parser would see uint4+unknown and could pick the uint4 operator. But that would 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 ma

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

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

pelling since there isn't an interoperability issue. -- 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] overlaps performance

keys aren't a prefix of the index pathkeys. We would have to do a full index scan but the cost 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 S

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

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

figure out what access method is best for finding the candidate record. That could mean using the primary key index, or it could mean using some other index (perhaps a partial index for example). It would be nice if there was a way for Slony to express to the server that really, it only needs any

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-

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

kets. That isn't going to win over btree which is already doing a binary search. 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 thra

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

> enhancement I can think of that eventually made it into a standard, was first > implemented within a popular product, and then demanded as a standard to be > applied to all other products. C99? SMTP? NTP? It tends to be important for network protocols since there's no gain in havi

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 ta

<    1   2   3   4   5   6   7   8   9   10   >