Re: [HACKERS] About numeric division again

assume you're right about there being bigger problems but I don't follow how the division is actually being done in enough detail to judge that for my self. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql

Re: [HACKERS] [GENERAL] ANALYZE getting dead tuple count hopelessly wrong

other processes after all... -- 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

Re: [HACKERS] Scroll cursor oddity...

*on* rows. I'm not sure the standard entirely adopts that model however. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

Re: [HACKERS] Commit fest status

reviews. -- 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] Guessing future postgresql features

involved in. -- 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] Commitfest patches

Simon Riggs [EMAIL PROTECTED] writes: On Fri, 2008-03-28 at 09:08 +, Gregory Stark wrote: A more invasive form of this patch would be to assign and pin a buffer when the preread is done. That would men subsequently we would have a pinned buffer ready to go and not need to go back

Re: [HACKERS] Prereading using posix_fadvise

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

Re: [HACKERS] Prereading using posix_fadvise

want even larger prefetch sizes. -- 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

Re: [HACKERS] Commitfest patches

Bruce Momjian [EMAIL PROTECTED] writes: Gregory Stark wrote: Bruce, you seem to have removed one of my three patches from the queue. I would actually prefer you remove the other two and put back that one. It's the one I most urgently need feedback on to continue. I talked to Greg on IM

[HACKERS] Commitfest patches

. -- 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] Windows shared_buffers limitations

also possible something more subtle is going on. -- 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

Re: [HACKERS] TODO Item: Consider allowing control of upper/lower case folding of unquoted, identifiers

always been using unquoted identifiers you can set FetchHashKeyName to NAME_lc and it would continue to work. If you've been using a mixture of quoted and unquoted identifiers things would be trickier though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] advancing snapshot's xmin

reset xmin whenever you have no live snapshots then that job would be doing that between every INSERT statement. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via pgsql-hackers

Re: [HACKERS] advancing snapshot's xmin

only set xmin once when we set the serializable snapshot. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

Re: [HACKERS] advancing snapshot's xmin

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Uhm, yeah, I somehow didn't write was I was thinking. I didn't mean to say we would be taking a new snapshot for each INSERT but that we would be resetting xmin for each INSERT. Whereas currently we only set xmin once

Re: [HACKERS] TRUNCATE TABLE with IDENTITY

with the semantics of sequences so I don't imagine attempting to shoehorn sequences into these clauses is likely to pan out. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] writing a MIN(RECORD) aggregate

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

Re: [HACKERS] partial dump of patch queue to wiki

.) -- 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] writing a MIN(RECORD) aggregate

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

Re: [HACKERS] writing a MIN(RECORD) aggregate

Sam Mason [EMAIL PROTECTED] writes: On Tue, Mar 25, 2008 at 06:58:06PM +, Gregory Stark wrote: The main thing I wanted to avoid was an explosion of sub-queries that you get with DISTINCT ON style queries. For example, with record style syntax, I can do: SELECT i, (MIN((j,k))).k AS ka

Re: [HACKERS] writing a MIN(RECORD) aggregate

to turn into quite an overhaul of record handling in PG. It would also remove the nice syntactic trick that a.b identifies the field b from table a, and s.a.b means that the above is in schema s. Yeah, to disambiguate it you have to use (r).i -- Gregory Stark EnterpriseDB http

Re: [HACKERS] Proposal: new ereport option errdetail_log

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

Re: [HACKERS] Proposal: new ereport option errdetail_log

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: I wonder how useful it is to output process ids at all. And for that matter whether leaking process ids alone could be considered a security risk. Seems overly paranoid, especially considering we've output

Re: [HACKERS] [pgsql-www] New email list for emergency communications

the archives to have a URL to go straight to a message-id and Bruce generated a list all on one page including comments and message-ids then I could process them all into a wiki page in a few hours. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] [pgsql-www] New email list for emergency communications

of how we tackle this list anyways. Magnus or Dave? Is there anything I can help with to get the URL to message-ids going? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] [pgsql-www] New email list for emergency communications

around with this. I should be able to snarf in the mbox and format a wiki page with the comments from js-kit and links to the message-id. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql-hackers mailing

Re: [HACKERS] Commit Fest

or applied from that list, but only Bruce can do that. Tom's berated Bruce once for not focusing on the commitfest so I suspect that may happen soon. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support! -- Sent via pgsql

Re: [HACKERS] Text - C string

for text_to_cstring etc. I can see the logic for the above but it's just such a pain to type... Fwiw I didn't actually find text_cstring confusing because all our sql cast functions are defined that way. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] Unique Constraints using Non-Unique Indexes

the uniqueness check. Could you still do that in this case? I don't immediately see any problems aside from reduced concurrency but this code isn't really my forté. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning -- Sent via

Re: [HACKERS] [Fwd: Re: [PATCHES] 64-bit CommandIds]

the ability to run vacuum. Also, we still have hope that the visibility map info will make running vacuum even less of an imposition. All that said I don't really see much reason not to make it an option. I just don't think anyone really needs it. In 5-10 years though... -- Gregory Stark

Re: [HACKERS] Sort Refinement

tuples? Also, I wonder how expensive checking the level break key on every tuple will be. I don't think it invalidates the approach but it has to be taken into account. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services

Re: [HACKERS] count(*) performance improvement ideas

the global xmin instead of your real xid people would get the same result and you could reclaim the space much much sooner. Locking the table kind of sucks though. And crash recovery would be a problem. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

Re: [HACKERS] New style of hash join proposal

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: We currently execute a lot of joins as Nested Loops which would be more efficient if we could batch together all the outer keys and execute a single inner bitmap index scan for all of them together. Please give

Re: [HACKERS] New style of hash join proposal

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Please give an example of what you're talking about that you think we can't do now. Note that we're doing a full sequential scan of a even though we've already finished hashing b

Re: [HACKERS] Rewriting Free Space Map

to regenerate a map we could do it in a new relfilenode and swap it in like we do with heap rewrites. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] Commit fest?

we use for the search engine on the web site? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] New style of hash join proposal

Gregory Stark [EMAIL PROTECTED] writes: It would be ideal if it could scan the invoices using an index, toss them all in a hash, then do a bitmap index scan to pull out all the matching detail records. If there are multiple batches it can start a whole new index scan for the each

Re: [HACKERS] New style of hash join proposal

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: It would be ideal if it could scan the invoices using an index, toss them all in a hash, then do a bitmap index scan to pull out all the matching detail records. If there are multiple batches it can start a whole new

Re: [HACKERS] [PATCHES] [0/4] Proposal of SE-PostgreSQL patches

true that it's best to post a plan and have discussion prior to developing big patches. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] Rewriting Free Space Map

of and the total number of inodes being referenced. -- 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

Re: [HACKERS] New style of hash join proposal

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: I don't understand which part of we can do that now isn't clear to you. Uh, except we can't. I already demonstrated that we could. If the problem is that the planner is cutting

Re: [HACKERS] New style of hash join proposal

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: I already demonstrated that we could. We seem to be talking past each other. The plan you showed is analogous but using a plain old index scan. That's only because that seemed

Re: [HACKERS] Better error message for select_common_type()

and must do better. Do we have something more helpful than branches 3 and 5? Perhaps printing the actual transformed expressions? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! -- Sent via

Re: [HACKERS] New style of hash join proposal

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Nested Loop (cost=5.39..198.81 rows=51 width=244) - HashAggregate (cost=1.06..1.11 rows=5 width=4) - Seq Scan on int4_tbl b (cost=0.00..1.05 rows=5 width=4) - Bitmap Heap

Re: [HACKERS] Commit fest?

Any chance we could put that on the actual listing page somehow. perhaps in a tiny font?? I want to be able to copy the thread and get enough information for future reference. Also, any chance you could use the permanent urls in the thread listing? -- Gregory Stark EnterpriseDB http

Re: [HACKERS] Commit fest?

the message-id's of all the messages and the comments on the same page. That way I can dump the data into a text file to experiment with. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-hackers

Re: [HACKERS] Commit fest?

/patches/dded9117101d6b0e1b8357066b9df9cd.html was not found on this server. -- 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

Re: [HACKERS] Commit fest?

Bruce Momjian [EMAIL PROTECTED] writes: Gregory Stark wrote: Bruce Momjian [EMAIL PROTECTED] writes: bruce wrote: Yea, that is a big problem because the URLs are dynamic. I have the comments based on message id but there is no way to hook that to a URL. I have modified the code

Re: [HACKERS] Commit fest?

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Actually, is it just me or has the whole patch queue disappeared? Everything under /mhonarc/patches seems to be gone. /mhonarc? The URL I've always used is http://momjian.us/cgi-bin/pgpatches Yeah, but note

Re: [HACKERS] [DOCS] pg_total_relation_size() and CHECKPOINT

at the time of insert might still be poor, but how could we lose after we've promised the data is committed? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] Commit fest?

think would make a good candidate? Or should I just pick a random one? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

[HACKERS] aclitem out/in don't work

I'm done what I'm doing. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [HACKERS] [ADMIN] Encoding problems with migration from 8.0.14 to 8.3.0 on Windows

Tom Lane [EMAIL PROTECTED] writes: I think this is a must fix bug for 8.3.1, anyone disagree? Agreed. It seems we should collect cases like this for the regression tests. The only one I was aware of previously was the Turkish one. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] aclitem out/in don't work

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: The output of aclitem can't be read back back in as an aclitem: postgres=# select relacl::text from pg_class limit 1; relacl {=r/stark} (1 row) postgres=# select relacl::text::aclitem

Re: [HACKERS] [COMMITTERS] pgsql: Add: o Add SQLSTATE severity to PGconn return status

. But that's more of a positive assertion that if nobody else is doing something they're responsible for getting it done rather than a negative assertion that nobody else should be helping. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7

Re: [HACKERS] count(*) performance improvement ideas

incremental changes means for each aggregate where it's meaningful though. Then it would require some magic in the optimizer to recognize when piece of the query can be satisfied by a materialized view. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's

Re: [HACKERS] Maximum statistics target

when that happens). That would remove the screw case the original poster had where he needed to scan a large portion of the table to see at least one of every value even though there were only 169 distinct values. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me

Re: [HACKERS] [Fwd: Re: [PATCHES] 64-bit CommandIds]

be the actual hard part. Do phantom command ids mean this all just works magically? Ie, the limit of 2^32 cmin,cmax pairs is still there but as long as you don't have to store more than that many you get to have 2^64 raw ephemeral commandids? -- Gregory Stark EnterpriseDB http

Re: [HACKERS] pg_dump additional options for performance

think of review as equivalent to commit. But patch authors often want to get some confirmation they're on the right track before they move on the next step. As a result many patches kind of get stuck in a catch-22 where they're not ready for review and no ready for development either. -- Gregory

Re: [HACKERS] Read-ahead and parallelism in redo recovery

a single buffer of read-ahead from the index block's next pointer but that's about it. Luckily it seems to me that bitmap index scans are much more likely to be chosen in the cases where there's a big gain anyways. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com

Re: [HACKERS] Bulk loading performance improvements

for 7.25% of CPU. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail

Re: [HACKERS] Proposed changes to DTrace probe implementation

at the standard database SNMP MIB counters would give us a place to start for upward facing events people want to trace for databases in general. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning ---(end

Re: [HACKERS] pg_dump additional options for performance

be the other piece of the puzzle but personally I'm not sure how to tackle that. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! ---(end of broadcast)--- TIP 4: Have you searched

Re: [HACKERS] pg_dump additional options for performance

or any background in pg_dump/pg_restore code. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send

Re: [HACKERS] Questions about indexes with text_pattern_ops

) WHERE b ~~ ''; That uses the same operator that the LIKE clause will use for the index range. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning ---(end of broadcast)--- TIP

Re: [HACKERS] Questions about indexes with text_pattern_ops

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Hm, for a simple = or I think it doesn't matter which operator class you use. For or it would produce different answers. Postgres isn't clever enough to notice that this is equivalent though so I think you would

Re: [HACKERS] Tuning 8.3

could pool or batch at a higher level and have fewer sessions active at all. You don't win any performance by trying to do more things simultaneously if they're just competing for cpu timeslices or i/o bandwidth. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained

Re: [HACKERS] Questions about indexes with text_pattern_ops

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: I'm intending to get rid of ~=~ and ~~ for 8.4; there's no longer any reason why those slots in the pattern_ops classes can't be filled by the plain = and operators

Re: [HACKERS] Questions about indexes with text_pattern_ops

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: How so? If you think this change is a bad idea you'd better speak up PDQ. Well I think it's fine for 'foo ' != 'foo' even if they sort similarly. But I'm not sure it makes sense

Re: [HACKERS] RFP: Recursive query in 8.4

[This message is mostly for the benefit of the list -- he and I already talked a bit about this here at FOSDEM. Ishii-san, if you have a chance we should sit down and talk about this in more detail before we leave!] Tatsuo Ishii wrote: On Tue, Feb 19, 2008 at 3:36 AM, Tatsuo Ishii [EMAIL

Re: [HACKERS] VARATT_EXTERNAL_GET_POINTER is not quite there yet

* which could be passed to VARDATA_ANY and VARDATA_ANY_EXHDR but not manipulated directly. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! ---(end of broadcast

Re: [HACKERS] VARATT_EXTERNAL_GET_POINTER is not quite there yet

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: I can't say that I find this a nice clean solution; but does anyone have a better one? I'm thinking instead of having struct varlena (which you're not allowed to safely use any

Re: [HACKERS] failed assertion in toasting code

figured out where the error is yet though. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! ---(end of broadcast)--- TIP 6: explain analyze

Re: [HACKERS] failed assertion in toasting code

of trying to compress them first with: ALTER column SET STORAGE EXTERNAL -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning ---(end of broadcast)--- TIP 1: if posting/reading

Re: [HACKERS] failed assertion in toasting code

Gregory Stark [EMAIL PROTECTED] writes: CREATE TYPE image ( INPUT = image_in, OUTPUT = image_out, INTERNALLENGTH = -1, STORAGE = external ); ALTER column SET STORAGE EXTERNAL Hum. I just noticed that you had set STORAGE = external in your type

[HACKERS] generating non-unicode 8-bit text data in SQL_ASCII encoding

=# select char((random()*255)::integer+1); ERROR: char out of range postgres=# select char((random()*255)::integer+1); ERROR: char out of range -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support

[HACKERS] More char()/ascii()

Also, I thought we said this would be an error: postgres=# select length(char(0)); length 0 (1 row) -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training

Re: [HACKERS] failed assertion in toasting code

to work in 8.3 any longer. You have to change this to: SET_VARSIZE(im, out_len+VARHDRSZ) And you have to access the length with VARSIZE_ANY_EXHDR() (or a few other macros but that's the most convenient). Phew. You had me scared there. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] More char()/ascii()

Andrew Dunstan [EMAIL PROTECTED] writes: Gregory Stark wrote: Also, I thought we said this would be an error: postgres=# select length(char(0)); length 0 (1 row) IIRC, we said chr(0) would give you an error, and it does. I don't recall any discussion of char(0

Re: [HACKERS] Permanent settings

their automatically maintained data. Apache used to be done like this on Debian (now it's a bit more complex using a directory, but the same idea). Emacs's custom.el package can be set up in a similar way where custom.el edits a separate file which you include from your .emacs. -- Gregory Stark

Re: [HACKERS] ANALYZE to be ignored by VACUUM

by an index. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster

Re: [HACKERS] Permanent settings

can warn that the change is ineffective. I think on balance the include file method is so much simpler that I prefer it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training

Re: [HACKERS] Permanent settings

Magnus Hagander [EMAIL PROTECTED] writes: On Tue, Feb 19, 2008 at 04:58:21PM +, Gregory Stark wrote: The include file method is workable but isn't perfect. What happens if a user connects with pgadmin and changes a parameter but that parameter is overridden by a variable in the config

Re: [HACKERS] Doubt in IndexScanDescData

One thing you might be missing is that indexes are relations too. They're a bit different than heap relations (ie tables) but they share enough structure that it's worth using the same datatypes to represent both. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me

Re: [HACKERS] Patch review

at it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! ---(end of broadcast)--- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail

Re: [HACKERS] Patch review

is it blocking on? and who is it blocking on? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication support! ---(end of broadcast)--- TIP 6: explain analyze is your friend

Re: [HACKERS] Patch review

Bruce Momjian [EMAIL PROTECTED] writes: Gregory Stark wrote: Bruce Momjian [EMAIL PROTECTED] writes: For the patches lists I need to take sometimes entire threads, sometimes groups of comments, and store them in a format so people can review them as a digest. Why do you need to do

Re: [HACKERS] Patch review

. They're two separate, but related, things. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's On-Demand Production Tuning ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore

Re: [HACKERS] Locale vs LIKE

Stephen Denne [EMAIL PROTECTED] writes: i.e. Do I still have to either initdb --locale=C or explicitly use text_pattern_ops? yes, if you want an index to be used -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support

Re: [HACKERS] AS by the syntax of table reference.(8.4 proposal)

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: But yeah, c_expr isn't enough. We really need {a,b}_expr sans postfix expressions. How's that going to help? As long as postfix operators exist at all, SELECT a + b, ... is going to be ambiguous

Re: [HACKERS] Patch review

is as vague as a tracker. As soon as our process changes the tracker will be obsolete whereas a problem-specific solution like reviewboard will always be useful as long as there are patches to review. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian

Re: [HACKERS] AS by the syntax of table reference.(8.4 proposal)

Tom Lane [EMAIL PROTECTED] writes: Gregory Stark [EMAIL PROTECTED] writes: Sure, just like a + + b is ambiguous. We define an arbitrary choice and tell people to put parentheses if they want the other. It's not too hard to write SELECT (a +) b, ... if you want an alias. Besides, nobody uses

Re: [HACKERS] AS by the syntax of table reference.(8.4 proposal)

just doesn't sound safe. There are other rules that have a %prec on the rule itself, does that not work here? *off to read the fine manual now* -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL

Re: [HACKERS] AS by the syntax of table reference.(8.4 proposal)

as a regular a_expr and then check for that in the target_el rule or in parse analysis and pull the ColId out. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training! ---(end

[HACKERS] Patch review

on the wiki? I could download the mbox files from the web site and filter them into a table. Some part of me thinks this data should be in a postgres database so I can do SQL queries against it to find a good patch to review. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask

Re: [HACKERS] Page-at-a-time Locking Considerations

the persistent store. One downside of using mmap though would be that we would be sacrificing address space. Regardless of how much of the clog is actually being used we would be losing address space large enough to cover all the clog we might need. -- Gregory Stark EnterpriseDB http

Re: [HACKERS] PostgreSQL 8.4 development plan

it would allow two non-committers to collaborate, something which we can't really do effectively now. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support! ---(end of broadcast)--- TIP 4

Re: [HACKERS] Why are we waiting?

or sitting runnable waiting for a timeslice. Was this with your patch to raise the size of the clog lru? What is MaxBackends actually set to for the runs. Is it the same even when you're actually running with fewer backends? -- Gregory Stark EnterpriseDB http

Re: [HACKERS] PostgreSQL 8.4 development plan

would hazard it's more widely used than CVS amongst open source projects. Therefore it *doesn't* have any poor choices of dependencies. For what it's worth I think GIT is a better fit for our needs. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's

Re: [HACKERS] Why are we waiting?

to be directly comparable. We could have a problem with cache line aliasing on only one or the other for example. But that is a pretty striking difference. Does the 8.3 run complete more transactions in that time? -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about

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