Re: [HACKERS] Testing extension upgrade scripts

da...@kineticode.com ("David E. Wheeler") writes: > You should blog this. He just did, using the SMTP protocol... -- select 'cbbrowne' || '@' || 'acm.org'; http://linuxdatabases.info/info/postgresql.html Where do you want to Tell Microsoft To Go Today? -- Sent via pgsql-hackers mailing list (pg

Re: [HACKERS] Re: Why our counters need to be time-based WAS: WIP: cross column correlation ...

j...@agliodbs.com (Josh Berkus) writes: >> I don't understand what you're talking about at all here. I think >> there are a lot of unsolved problems in monitoring but the one thing >> I think everyone is pretty clear on is that the right way to export >> metrics like these is to export a counter an

Re: [HACKERS] CommitFest 2011-01 as of 2011-02-04

robertmh...@gmail.com (Robert Haas) writes: > It does, but frankly I don't see much reason to change it, since it's > been working pretty well on the whole. Andrew was on point when he > mentioned that it's not obvious what committers get out of working on > other people's patches. Obviously, the

Re: [HACKERS] why two dashes in extension load files

t...@sss.pgh.pa.us (Tom Lane) writes: > Peter Eisentraut writes: >> On mån, 2011-02-14 at 10:13 -0500, Tom Lane wrote: >>> Peter Eisentraut writes: Why do the extension load files need two dashes, like xml2--1.0.sql? Why isn't one enough? > >>> Because we'd have to forbid dashes in exte

Re: [HACKERS] Range Types - efficiency

pg...@j-davis.com (Jeff Davis) writes: > On Wed, 2011-02-09 at 16:20 -0500, Chris Browne wrote: >> rangetest@localhost-> explain analyze select * from some_data where >> '[2010-01-01,2010-02-01)'::daterange @> whensit; >>

[HACKERS] Range Types - efficiency

One of the things I'd particularly like to use range types for is to make it easier to construct range-related queries. Classic example is that of reports that work on date ranges. I create a table that will have transaction data: CREATE TABLE some_data ( id serial, whensit date -- A

Re: [HACKERS] postponing some large patches to 9.2

pg...@j-davis.com (Jeff Davis) writes: > On Tue, 2011-02-08 at 15:10 -0500, Chris Browne wrote: >> It's more than a bit sad... The RangeType change has the massive merit >> of enabling some substantial development changes, where we can get rid >> of whole classes

Re: [HACKERS] postponing some large patches to 9.2

pg...@j-davis.com (Jeff Davis) writes: > On Tue, 2011-02-08 at 06:57 -0500, Stephen Frost wrote: >> * Robert Haas (robertmh...@gmail.com) wrote: >> > - Range Types. This is a large patch which was submitted for the >> > first time to the last CommitFest of the cycle, and the first version >> > tha

Re: [HACKERS] postponing some large patches to 9.2

sfr...@snowman.net (Stephen Frost) writes: > * Robert Haas (robertmh...@gmail.com) wrote: >> - Range Types. This is a large patch which was submitted for the >> first time to the last CommitFest of the cycle, and the first version >> that had no open TODO items was posted yesterday, three-quarters

Re: [HACKERS] Sync Rep for 2011CF1

dp...@pgadmin.org (Dave Page) writes: > On Mon, Feb 7, 2011 at 6:55 PM, Robert Haas wrote: >> On Mon, Feb 7, 2011 at 12:43 PM, Tom Lane wrote: >>> Robert Haas writes: ... Well, the current CommitFest ends in one week, ... >>> >>> Really?  I thought the idea for the last CF of a development

Re: [HACKERS] OpenVMS - an effort which needs guidance and support.

peder...@ccsscorp.com ("Bill Pedersen") writes: > I look forward to hearing from people in the PostgreSQL community as well as > from others interested in this effort. To a number of us, it's academically interesting, though, as we don't have VMS systems, it's not likely to be super-easy to assist

Re: [HACKERS] WIP: RangeTypes

pg...@j-davis.com (Jeff Davis) writes: > On Fri, 2011-01-28 at 09:17 -0800, David Fetter wrote: >> For consistency, and in order not to continue our atrocious naming >> tradition, I'd like to propose that the above be named timestamprange >> (tsrange for short) and timestamptzrange (tstzrange for

Re: [HACKERS] Caution when removing git branches

and...@dunslane.net (Andrew Dunstan) writes: > On 01/27/2011 11:29 AM, Tom Lane wrote: >> Given that nobody is supposed to push temporary branches to the master >> repo anyway, an intended branch removal should be a pretty darn rare >> event. Now, our committers all seem to be pretty careful peopl

Re: [HACKERS] ALTER TABLE ... ADD FOREIGN KEY ... NOT ENFORCED

si...@2ndquadrant.com (Simon Riggs) writes: > I just wanted to point out that the patch submitted here does not allow > what is requested here for FKs (nor indexes). That's fine; I was trying to support the thought that there was something useful about this idea. Being able to expressly deactivat

Re: [HACKERS] Review: compact fsync request queue on overflow

robertmh...@gmail.com (Robert Haas) writes: > On Mon, Jan 17, 2011 at 8:23 PM, Greg Smith wrote: >> Quite.  It's taken me 12 days of machine time running pgbench to find the >> spots where this problem occurs on a system with a reasonably sized >> shared_buffers (I'm testing against 256MB).  It's

[HACKERS] Review: compact fsync request queue on overflow

I have been taking a peek at the following commitfest item: https://commitfest.postgresql.org/action/patch_view?id=497 Submission: - I had to trim a little off the end of the patch to apply it, but that's likely the fault of how I cut'n'pasted it. It applied cleanly against HEAD. - I obse

Re: [HACKERS] [COMMITTERS] pgsql: Implement remaining fields of information_schema.sequences view

pete...@gmx.net (Peter Eisentraut) writes: > Implement remaining fields of information_schema.sequences view > > Add new function pg_sequence_parameters that returns a sequence's start, > minimum, maximum, increment, and cycle values, and use that in the view. > (bug #5662; design suggestion by Tom

Re: [HACKERS] C++ keywords in headers

pete...@gmx.net (Peter Eisentraut) writes: > On mån, 2010-12-27 at 12:33 -0500, Andrew Dunstan wrote: >> On a more general point, it would be useful to have some >> infrastructure for running quality checks like this and publishing >> the results. We should be way beyond the point where we rely on

Re: [HACKERS] psql expanded auto

pete...@gmx.net (Peter Eisentraut) writes: > I have often found myself wanting that psql automatically switch between > normal and \x mode depending on the width of the output. Would others > find this useful? I haven't tested the patch, but that *does* sound generally useful. It's no fun trying

Re: [HACKERS] ALTER TABLE ... ADD FOREIGN KEY ... NOT ENFORCED

t...@sss.pgh.pa.us (Tom Lane) writes: > Robert Haas writes: >> ... On the >> other hand, there's clearly also a use case for this behavior. If a >> bulk load of prevalidated data forces an expensive revalidation of >> constraints that are already known to hold, there's a real chance the >> DBA w

Re: [HACKERS] Anyone for SSDs?

loureir...@gmail.com (Daniel Loureiro) writes: >> You can believe whatever you want, that doesn't make it true. > completely agree. Like yours, Its just my point of view, not the reality. > > I agree with some points here, but I wondering how many good ideas are > killed with the thought: "this wil

Re: [HACKERS] would hw acceleration help postgres (databases in general) ?

j...@nasby.net (Jim Nasby) writes: > On Dec 10, 2010, at 6:18 PM, Jeff Janes wrote: >> On Fri, Dec 10, 2010 at 3:09 PM, Hamza Bin Sohail wrote: >>> >>> Hello hackers, >>> >>> I think i'm at the right place to ask this question. >>> >>> Based on your experience and the fact that you have written

Re: [HACKERS] unlogged tables

t...@sss.pgh.pa.us (Tom Lane) writes: > "Kevin Grittner" writes: >> Robert Haas wrote: >>> Simon Riggs wrote: Note that DB2 uses the table modifier VOLATILE to indicate a table that has a widely fluctuating table size, for example a queue table. > >>> the fact that DB2 uses that

Re: [HACKERS] Final(?) proposal for wal_sync_method changes

x...@thebuild.com (Christophe Pettus) writes: > On Dec 7, 2010, at 2:43 PM, Josh Berkus wrote: >> Because nobody sane uses OSX on the server? > > The XServe running 10.5 server and 9.0.1 at the other end of the > office takes your remark personally. :) I'd heard that Apple had cancelled XServe. [

Re: [HACKERS] Two different methods of sneaking non-immutable data into an index

mmonc...@gmail.com (Merlin Moncure) writes: > On Thu, Aug 5, 2010 at 12:59 PM, Chris Browne wrote: >> mmonc...@gmail.com (Merlin Moncure) writes: >>> On Wed, Aug 4, 2010 at 9:31 PM, Robert Haas wrote: >>>> On Wed, Aug 4, 2010 at 6:43 PM, Merlin Moncure wrote: >&

Re: [HACKERS] Two different methods of sneaking non-immutable data into an index

mmonc...@gmail.com (Merlin Moncure) writes: > On Wed, Aug 4, 2010 at 9:31 PM, Robert Haas wrote: >> On Wed, Aug 4, 2010 at 6:43 PM, Merlin Moncure wrote: >>> *) also, isn't it possible to change text cast influencing GUCs 'n' >>> times per statement considering any query can call a function and a

Re: [HACKERS] Concurrent MERGE

robertmh...@gmail.com (Robert Haas) writes: > On Thu, Aug 5, 2010 at 11:43 AM, Simon Riggs wrote: >> Looks like MERGE is progressing well. >> >> At 2010 Dev Mtg, we put me down to work on making merge work >> concurrently. That was garbled slightly and had me down as working on >> predicate lockin

Re: [HACKERS] SHOW TABLES

si...@2ndquadrant.com (Simon Riggs) writes: > Just for the record, I've never ever met anyone that said "Oh, this > \d syntax makes so much sense. I'm a real convert to Postgres now > you've shown me this". The reaction is always the opposite one; > always negative. Which detracts from our efforts

[HACKERS] Buildfarm + Git tryouts

I'm trying to start preparing buildfarm nodes for the upcoming Git migration, and have run into a few issues. I speculate that -hackers is one of the better places for this to get discussed; if it should be elsewhere, I'm sure Andrew Dunstan won't be shy to redirect this :-). What I was hoping to

Re: [HACKERS] Check constraints on non-immutable keys

mag...@hagander.net (Magnus Hagander) writes: >> I concur with the thought that the most useful solution might be a way >> to tell pg_restore to remove or disable check constraints. > > Uh, say what? Are you saying pg_restore should actually remove > something from the database schema? And thus no

Re: [HACKERS] Exposing the Xact commit order to the user

gsst...@mit.edu (Greg Stark) writes: > On Wed, Jun 2, 2010 at 6:45 PM, Chris Browne wrote: >> It would make it easy to conclude: >> >>   "This next transaction did 8328194 updates.  Maybe we should do >>   some kind of checkpoint (e.g. - commit transaction or

Re: [HACKERS] Exposing the Xact commit order to the user

br...@momjian.us (Bruce Momjian) writes: > Jan Wieck wrote: >> The point is not that we don't have that information now. The point is >> having a hint BEFORE wading through possibly gigabytes of WAL or log data. >> >> If getting that information requires to read all the log data twice or >> the

Re: [HACKERS] Exposing the Xact commit order to the user

heikki.linnakan...@enterprisedb.com (Heikki Linnakangas) writes: > On 24/05/10 19:51, Kevin Grittner wrote: >> The only thing I'm confused about is what benefit anyone expects to >> get from looking at data between commits in some way other than our >> current snapshot mechanism. Can someone expla

Re: [HACKERS] Exposing the Xact commit order to the user

d...@csail.mit.edu (Dan Ports) writes: > I'm not clear on why the total rowcount is useful, but perhaps I'm > missing something obvious. It would make it easy to conclude: "This next transaction did 8328194 updates. Maybe we should do some kind of checkpoint (e.g. - commit transaction or s

Re: [HACKERS] Add column if not exists (CINE)

robertmh...@gmail.com (Robert Haas) writes: > On Wed, Apr 28, 2010 at 1:40 PM, Dimitri Fontaine > wrote: >> Robert Haas writes: >>> Well, how would you define CREATE OR REPLACE TABLE?  I think that >>> doesn't make much sense, which is why I think CREATE IF NOT EXISTS is >>> a reasonable approach

Re: [HACKERS] Proposal: Add JSON support

robertmh...@gmail.com (Robert Haas) writes: > On Tue, Mar 30, 2010 at 8:58 PM, Josh Berkus wrote: >>> I'd think that you could get quite a long ways on this, at least doing >>> something like dbslayer without *necessarily* needing to do terribly >>> much work inside the DB engine. >> >> There's ac

Re: [HACKERS] Proposal: Add JSON support

joeyadams3.14...@gmail.com (Joseph Adams) writes: > I introduced myself in the thread "Proposal: access control jails (and > introduction as aspiring GSoC student)", and we discussed jails and > session-local variables. But, as Robert Haas suggested, implementing > variable support in the backend

Re: [HACKERS] An idle thought

si...@2ndquadrant.com (Simon Riggs) writes: > On Tue, 2010-03-16 at 15:29 +, Greg Stark wrote: > >> big batch delete > > Is one of the reasons for partitioning, allowing the use of truncate. Sure, but it would be even nicer if DELETE could be thus made cheaper without needing to interfere with

Re: [HACKERS] SQL compatibility reminder: MySQL vs PostgreSQL

francois.pe...@free.fr (François Pérou) writes: > * I am very surprised by the SQL level of Php developers. The example > Drupal developers trying to rewrite SQL queries dynamically adding > DISTINCT clause is just an example. So don't expect them to understand > the difference between MySQL and Po

Re: [HACKERS] Anyone know if Alvaro is OK?

scrawf...@pinpointresearch.com (Steve Crawford) writes: > Marc G. Fournier wrote: >> >> Is there a higher then normal amount of earthquakes happening >> recently? haiti, japan just had one for 6.9, there was apparently >> one in illinos a few weeks back, one on the Russia/China/N.Korean >> border a

Re: [HACKERS] LISTEN/NOTIFY and notification timing guarantees

t...@sss.pgh.pa.us (Tom Lane) writes: > Merlin Moncure writes: >> On Tue, Feb 16, 2010 at 10:38 AM, Tom Lane wrote: >>> 2. Add an extra lock to serialize writers to the queue, so that messages >>> are guaranteed to be added to the queue in commit order.  As long as > >> fwiw, I think you're defin

Re: [HACKERS] OpenVMS?

scra...@hub.org ("Marc G. Fournier") writes: > On Tue, 16 Feb 2010, Bruce Momjian wrote: > >> I hate to pour cold water on this, but why is it worth adding >> support for a platform that has such marginal usage. > > Because someone feels like dedicating their resources to it ... ? But adding it in

Re: [HACKERS] OpenVMS?

rocr...@gmx.de (Robert Doerfler) writes: > On Tue, 16 Feb 2010, Bruce Momjian wrote: > >> Marc G. Fournier wrote: >>> On Tue, 16 Feb 2010, Bruce Momjian wrote: >>> I hate to pour cold water on this, but why is it worth adding support for a platform that has such marginal usage. >>> >>> Be

Re: [HACKERS] Confusion over Python drivers

kevina...@hotmail.com (Kevin Ar18) writes: > Of course all of this is from the perspective of Python users. Of > course, you have your own features that you want from your end (from > PostgreSQL's perspective). Perhaps this info would help you to know > which avenue to pursue. No, those seem lik

Re: [HACKERS] Add .gitignore files to CVS?

bada...@gmail.com (Alex Hunsaker) writes: > On Fri, Jan 8, 2010 at 02:03, Magnus Hagander wrote: >> You can always create your own branch with just the .gitignore files >> and merge that into whatever you're working on :) > > The only thing annoying about that is if you generate diffs ala git > di

Re: [HACKERS] RFC: PostgreSQL Add-On Network

robertmh...@gmail.com (Robert Haas) writes: > On Fri, Jan 8, 2010 at 10:12 AM, Dave Page wrote: >>> I have long spoken against making Windows a second class citizen. But I >>> don't think David is going to do that (and I'll hound him if he does). But >>> that doesn't mean it has to be fully suppor

Re: [HACKERS] Thoughts on statistics for continuously advancing columns

j...@commandprompt.com ("Joshua D. Drake") writes: > On the other hand ANALYZE also: > > 1. Uses lots of memory > 2. Lots of processor > 3. Can take a long time > > We normally don't notice because most sets won't incur a penalty. We got a > customer who > has a single table that is over 1TB in siz

Re: [HACKERS] Has anyone used CLANG yet?

age...@themactionfaction.com ("A.M.") writes: [Much of interest elided... Cool to see that clang clearly *can* compile PostgreSQL...] > You are probably running configure with gcc, no? I was *attempting* to run configure using clang: CC=/usr/bin/clang ./configure --prefix=/home/chris/dbs/pos

[HACKERS] Has anyone used CLANG yet?

This is a C front end for the LLVM compiler... I noticed that it entered Debian/Unstable today: http://packages.debian.org/sid/main/clang I thought it would be interesting to see if PostgreSQL compiles with this, as an alternative compiler that should presumably become more and more available

Re: [HACKERS] Adding support for SE-Linux security

t...@sss.pgh.pa.us (Tom Lane) writes: > Robert Haas writes: >> On Mon, Dec 7, 2009 at 9:48 AM, Bruce Momjian wrote: >>> I wonder if we should rephrase this as, "How hard will this feature be >>> to add, and how hard will it be to remove in a few years if we decide we >>> don't want it?" > >> Yes,

Re: [HACKERS] New PostgreSQL Committers

dp...@pgadmin.org (Dave Page) writes: > Congratulations! +1 Congratulations, indeed, to this worthy set of developers! -- output = reverse("moc.liamg" "@" "enworbbc") http://linuxfinances.info/info/multiplexor.html "Power tends to corrupt and absolute power corrupts absolutely." -- First Bar

Re: [HACKERS] cvs chapters in our docs

pete...@gmx.net (Peter Eisentraut) writes: > On ons, 2009-11-25 at 16:27 +0100, Magnus Hagander wrote: >> Attached is a patch which adds a chapter to git in our documentation, >> around where we have several chapters about cvs today. It also removes >> a few very out of date comments about cvs > >

Re: [HACKERS] Listen / Notify - what to do when the queue is full

g...@turnstep.com ("Greg Sabino Mullane") writes: >> BTW, did we discuss the issue of 2PC transactions versus notify? >> The current behavior of 2PC with notify is pretty cheesy and will >> become more so if we make this change --- you aren't really >> guaranteed that the notify will happen, even t

Re: [HACKERS] next CommitFest

j...@commandprompt.com ("Joshua D. Drake") writes: > On Mon, 2009-11-16 at 11:31 -0500, Chris Browne wrote: > >> Ah, but the thing is, what was proposed wasn't "totally evilly >> draconian." >> >> There's a difference between: >>

Re: [HACKERS] next CommitFest

and...@dunslane.net (Andrew Dunstan) writes: > Robert Haas wrote: >> I am personally quite tired of reviewing patches for people who don't >> in turn review mine (or someone's). It makes me feel like not >> working on this project. If we can solve that problem without >> implementing a policy of

Re: [HACKERS] Proposal - temporal contrib module

arta...@comcast.net (Scott Bailey) writes: > Disk format - A period can be represented as [closed-closed], > (open-open), [closed-open) or (open-closed] intervals. Right now we > convert these to the most common form, closed-open and store as two > timestamptz's. I mentioned this at the 2009 PGCon

Re: [HACKERS] License clarification: BSD vs MIT

dp...@pgadmin.org (Dave Page) writes: > As Tom says though, the effect this has on users is zero. The licence > is still the same as its always been, regardless of what we say it is > based on or looks like. There may be a fairly miniscule one... There do exist "GPL zealots" that bash, as "not fr

Re: [HACKERS] Rules: A Modest Proposal

sfr...@snowman.net (Stephen Frost) writes: > * David Fetter (da...@fetter.org) wrote: >> On Sun, Oct 04, 2009 at 04:07:40PM -0400, Robert Haas wrote: >> > > The radical proposal was the RULE system.  It's been tested now, >> > > and it's pretty much failed. >> > >> > You still haven't explained w

Re: [HACKERS] 8.5 TODO: Add comments to output indicating version of pg_dump and of the database server

pete...@gmx.net (Peter Eisentraut) writes: > On Fri, 2009-09-25 at 16:59 -0400, Tom Lane wrote: >> "shakahsha...@gmail.com" writes: >> > From pg_dump/pg_restore section (9.2 of the Todo page on the >> > PostgreSQL Wiki), is the following item >> > "Add comments to output indicating version of pg

Re: [HACKERS] SE-PostgreSQL Specifications

s...@samason.me.uk (Sam Mason) writes: > On Sun, Jul 26, 2009 at 01:42:32PM +0900, KaiGai Kohei wrote: >> Robert Haas wrote: >> In some cases, the clearance of infoamtion may be changed. We often >> have dome more complex requirements also. > > OK, so there is some other trusted entity that has unf

Re: [HACKERS] New types for transparent encryption

a...@esilo.com (Andrew Chernow) writes: > Would the IV be regenerated every time the plaintext is updated, to > avoid using it twice? For instace: update t set text = 'abc' where id > = 1 . ISTM that the IV for OLD.text should be thrown away. > > Where would the key come from? Where would it be

Re: [HACKERS] [pgsql-www] commitfest.postgresql.org

robertmh...@gmail.com (Robert Haas) writes: > I suspect both are true, but in the unlikely event that we decide on > some massive change to the system, we can either run the DBs in > parallel as Tom suggests, or dump out the older data in Wiki markup > and post it on there. But I can't imagine what

Re: [HACKERS] New types for transparent encryption

gsst...@mit.edu (Greg Stark) writes: > However I have a different concern which hasn't been raised yet. > Encrypting lots of small chunks of data with the same key is a very > dangerous thing to do and it's very tricky to get right. Yeah, that's exactly the sort of thing that would be Most Useful

Re: [HACKERS] 8.5 development schedule

gsst...@mit.edu (Greg Stark) writes: > I would like to propose a different strategy. Instead of always > tackling all the smaller patches and leaving the big patches for last, > I would suggest we start with Hot Standby. > > In fact I would suggest as Hot Standby has already gotten a first pass > r

Re: [HACKERS] pre-proposal: permissions made easier

and...@dunslane.net (Andrew Dunstan) writes: > Jeff Davis wrote: >> On Mon, 2009-06-29 at 12:55 -0400, Tom Lane wrote: >> >>> I think it has to be looked at in comparison to more general >>> prospective-permissions schemes; >> >> When I searched google for "prospective permissions", all I found we

Re: [HACKERS] conditional dropping of columns/constraints

robertmh...@gmail.com (Robert Haas) writes: > On Mon, May 4, 2009 at 10:10 AM, Andres Freund wrote: >> Would a patch adding 'IF EXISTS' support to: >> - ALTER TABLE ... DROP COLUMN >> - ALTER TABLE ... DROP CONSTRAINT >> possibly be accepted? >> >> Having it makes the annoying task of writing/test

Re: [HACKERS] [ADMIN] License Issue

t...@sss.pgh.pa.us (Tom Lane) writes: > Korry Douglas writes: >>> Seems like the easy solution is to rip out the AIX files in your >>> server deployments ... or are you actually intending to support AIX? > >> AIX itself now offers the functions found in src/backend/port/ >> dynloader/aix.c so I t

Re: [HACKERS] A renewed plea for inclusion of zone.tab

and...@tao11.riddles.org.uk (Andrew Gierth) writes: > The usual conversation goes something like this (generally following > on from some discussion of how to do timezone conversions): > > Q: how do I get the list of available zone names? > > A: see pg_timezone_names > > Q: but there's 1650/1400

XML only working in UTF-8 - Re: [HACKERS] 8.4 open items list

j...@agliodbs.com (Josh Berkus) writes: > This one is also really bad, but probably only Doc-patchable. > However, can SQL/XML really be said to be core functionality if it > only works in UTF-8? > * BUG #4622: xpath only work in utf-8 server encoding Well, much of the definition of XML assume

Re: [HACKERS] Multi calendar system for pgsql

m.alimom...@gmail.com (Mohsen Alimomeni) writes: > I want to try to add a multi calendar system for pgsql. I want to > know if it will be accepted as a patch to pgsql? I would expect there to be nearly zero chance of such, at least in the form of a change to how dates are stored. As long as there

Re: [HACKERS] Simple postgresql.conf wizard

[EMAIL PROTECTED] ("Dave Page") writes: > On Fri, Nov 14, 2008 at 8:10 AM, Simon Riggs <[EMAIL PROTECTED]> wrote: >> >> On Fri, 2008-11-14 at 02:21 +, Gregory Stark wrote: >> >>> On the other hand what does occur to me in retrospect is that I regret >>> that I didn't think about how I was dispa

Re: [HACKERS] SQL5 budget

[EMAIL PROTECTED] (Alvaro Herrera) writes: > David Rowley escribió: > >> Or is sponsoring a feature paying money to people that already plan to >> implement something? > > Nobody on their mind would plan to implement the features being proposed > here ... I didn't look very far but it seems mainly

Re: [HACKERS] SQL5 budget

[EMAIL PROTECTED] ("Jonah H. Harris") writes: > On Sun, Nov 9, 2008 at 7:41 PM, Decibel! <[EMAIL PROTECTED]> wrote: >> I think you're barking up the wrong tree here; the community can't really do >> hacking for hire. If you want to pay for something to be implemented (which >> is great!), you'll ne

Re: [HACKERS] SQL/MED compatible connection manager

[EMAIL PROTECTED] (Martin Pihlak) writes: > Tons of details have been omitted, but should be enough to start discussion. > What do you think, does this sound usable? Suggestions, objections? Slony-I does some vaguely similar stuff in its handling of "connection paths"; here's the schema: create

Re: [HACKERS] PostgreSQL future ideas

[EMAIL PROTECTED] ("Jonah H. Harris") writes: > On Fri, Sep 26, 2008 at 11:52 AM, Andrew Dunstan <[EMAIL PROTECTED]> wrote: >>> Speaking of language choice, no one said that _all_ the source code would >>> need to be rewritten. It would be nice, for example, if PostgreSQL rewrote >>> the current GU

Re: [HACKERS] PostgreSQL future ideas

[EMAIL PROTECTED] (Andrew Dunstan) writes: > A.M. wrote: >> Speaking of language choice, no one said that _all_ the source code >> would need to be rewritten. It would be nice, for example, if >> PostgreSQL rewrote the current GUC system with a glue language like >> Lua (which is also very C-like).

Re: [HACKERS] PostgreSQL future ideas

[EMAIL PROTECTED] ("Gevik Babakhani") writes: >> Advantage of C++ is that it reduce lot of OO code written in >> C in PostgreSQL, but it is so big effort to do that without >> small gain. It will increase number of bugs. Do not forget >> also that C++ compiler is not so common (so good) on >> d

Re: [HACKERS] pgsql: Make LC_COLLATE and LC_CTYPE database-level settings.

[EMAIL PROTECTED] (Heikki Linnakangas) writes: > Log Message: > --- > Make LC_COLLATE and LC_CTYPE database-level settings. Collation and > ctype are now more like encoding, stored in new datcollate and datctype > columns in pg_database. > > This is a stripped-down version of Radek Strnad'

Re: [HACKERS] PostgreSQL future ideas

[EMAIL PROTECTED] ("Gevik Babakhani") writes: > It might look like an impossible goal to achieve.. But if there is > any serious plan/idea/ammo for this, I believe it would be very > beneficial to the continuity of PG. Actually, I imagine that such a rewrite would run a very considerable risk of i

Re: [HACKERS] Transaction Snapshots and Hot Standby

[EMAIL PROTECTED] (Heikki Linnakangas) writes: > Simon Riggs wrote: >> Taking snapshots from primary has a few disadvantages >> >> ... >> * snapshots on primary prevent row removal (but this was also an >> advantage of this technique!) > > That makes it an awful solution for high ava

Re: [HACKERS] Fast REVERSE() function?

[EMAIL PROTECTED] (hubert depesz lubaczewski) writes: > On Mon, Sep 08, 2008 at 11:20:18AM -0400, Chris Browne wrote: >> I've got a case where I need to reverse strings, and find that, oddly >> enough, there isn't a C-based reverse() function. >> A search turns up p

[HACKERS] Fast REVERSE() function?

I've got a case where I need to reverse strings, and find that, oddly enough, there isn't a C-based reverse() function. A search turns up pl/pgsql and SQL implementations: create or replace function reverse_string(text) returns text as $$ DECLARE reversed_string text; incoming alias for $1; BEGIN

Re: [HACKERS] Planner creating ineffective plans on LEFT OUTER joins

[EMAIL PROTECTED] (Simon Riggs) writes: > On Wed, 2008-06-25 at 23:34 -0400, Robert Haas wrote: >> I can predict that Tom will say that the planning time it would take >> to avoid this problem isn't justified by the number of queries that it >> would improve. > >> That's possible, but it's unfort

Re: [HACKERS] Overhauling GUCS

[EMAIL PROTECTED] (Greg Smith) writes: > On Fri, 6 Jun 2008, Heikki Linnakangas wrote: > >> Or perhaps we should explicitly mark the settings the tool has >> generated, and comment out: >> >> #shared_buffers = 32MB # commented out by wizard on 2008-06-05 >> shared_buffers = 1024MB # automaticall

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

[EMAIL PROTECTED] ("Andreas 'ads' Scherbaum") writes: > On Thu, 29 May 2008 23:02:56 -0400 Andrew Dunstan wrote: > >> Well, yes, but you do know about archive_timeout, right? No need to wait >> 2 hours. > > Then you ship 16 MB binary stuff every 30 second or every minute but > you only have some k

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

[EMAIL PROTECTED] (Tom Lane) writes: > As I said originally, we have no expectation that the proposed features > will displace the existing replication projects for "high end" > replication problems ... and I'd characterize all of Robert's concerns > as "high end" problems. We are happy to let tho

Re: [HACKERS] Protection from SQL injection

[EMAIL PROTECTED] (Florian Weimer) writes: > * Thomas Mueller: > >> What do you think about it? Do you think it makes sense to implement >> this security feature in PostgreSQL as well? > > Can't this be implemented in the client library, or a wrapper around it? > A simple approximation would be to

Re: [HACKERS] Protection from SQL injection

[EMAIL PROTECTED] (Alvaro Herrera) writes: > Darren Reed wrote: > >> Because interacting with the database is always through an action >> that you do and if you're being half way intelligent about it, you >> are always checking that each action succeeded before going on to >> the next. > > Hmm, it

Re: [HACKERS] we don't have a bugzilla

[EMAIL PROTECTED] (Andrew Dunstan) writes: > Raphaël Jacquot wrote: >> would seem like a good idea, no ? >> >> http://www.murrayc.com/blog/permalink/2008/04/25/postgresql-has-no-bugzilla/ > > Before you come trolling on this (or any other) subject, please read > the voluminous debates that have ta

Re: [HACKERS] MERGE Specification

[EMAIL PROTECTED] (Decibel!) writes: > On Apr 22, 2008, at 1:17 PM, Gregory Stark wrote: >> "Simon Riggs" <[EMAIL PROTECTED]> writes: >> >>> As I've said elsewhere, we could have it lock each row, its just more >>> overhead if we do and not necessary at all for bulk data merging. >>> >>> I'll pres

Re: [HACKERS] Problem with server/utils/snapmgr.h

[EMAIL PROTECTED] (Alvaro Herrera) writes: > Chris Browne wrote: > >> If I use: >> AC_CHECK_HEADER(utils/snapmgr.h, HAVE_SNAPMGR=1) >> >> this turns out to fail. Apparently autoconf wants to compile the >> #include file to validate that it's an OK #i

[HACKERS] Problem with server/utils/snapmgr.h

There's a new #include file that it turns out we need for Slony-I to reference, namely include/server/utils/snapmgr.h I tried adding an autoconf rule to Slony-I to check for its existence (goal then is to do a suitable #define so that we can #ifdef the #include, so that we #include this only with

Re: [HACKERS] TODO, FAQs to Wiki?

[EMAIL PROTECTED] (Bruce Momjian) writes: > I am impressed at the state of the May wiki patch queue: > > http://wiki.postgresql.org/wiki/CommitFest:May > > It is even tracking the psql wrap patch I am working on now. Aside: I have made a few little changes that oughtn't be too controversial:

Re: [HACKERS] get rid of psql welcome message

[EMAIL PROTECTED] (Stephen Frost) writes: > * Peter Eisentraut ([EMAIL PROTECTED]) wrote: >> Around >> it >> was proposed to truncate the psql welcome screen. What do you think about >> that? > > I'd recommend an option in .psq

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> Would it be a terrible idea to... >> >> - Draw the indent code from NetBSD into src/tools/pgindent > > I am not real eager to become maintainers of our own indent fork, which

Re: [HACKERS] MERGE SQL Statement

[EMAIL PROTECTED] (Simon Riggs) writes: >> Should there be a new rule option? ie. ON MERGE rules ? > > Maybe, but not as part of this project. That seems to warrant a bit of elaboration... If we're running a MERGE, and it performs an INSERT or UPDATE of a particular tuple in(to) a particular ta

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Bruce Momjian) writes: > Chris Browne wrote: >> >> Would it be a terrible idea to... >> >> >> >> - Draw the indent code from NetBSD into src/tools/pgindent >> >> - Build it _in place_ inside the code tree (e.g. - don't

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Bruce Momjian) writes: > Chris Browne wrote: >> [EMAIL PROTECTED] (Bruce Momjian) writes: >> > Magnus Hagander wrote: >> >> > And I think adopting surrounding naming, commeting, coding conventions >> >> > should come naturally as i

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Bruce Momjian) writes: > Magnus Hagander wrote: >> > And I think adopting surrounding naming, commeting, coding conventions >> > should come naturally as it can aide in copy-pasting too :) >> >> I think pg_indent has to be made a lot more portable and easy to use >> before that

Re: [HACKERS] Lessons from commit fest

[EMAIL PROTECTED] (Tom Lane) writes: > Magnus Hagander <[EMAIL PROTECTED]> writes: >> I think pg_indent has to be made a lot more portable and easy to use >> before that can happen :-) I've run it once or twice on linux machines, >> and it comes out with huge changes compared to what Bruce gets on

  1   2   3   >