On Wed, Oct 17, 2012 at 5:45 PM, Daniel Farina wrote:
> retort -- which is true, Heroku's user base is not provably
> representative of all users. But what else is there to go on, besides
> experiences of others, such as yours and Andrew's, or others?
Well, Heroku doesn't support Slony + Londist
On Thu, Oct 18, 2012 at 9:49 AM, Peter Geoghegan wrote:
> On 16 October 2012 15:26, Jan Wieck wrote:
>> This means that the transition time from the existing, trigger based
>> approach to the new WAL based mechanism will see both technologies in
>> parallel, which is no small thing to support.
>
On Thu, Oct 18, 2012 at 2:56 PM, Hannu Krosing wrote:
> * works as table on INSERTS up to inserting logical WAL record describing
> the
> insert but no data is inserted locally.
>
> with all things that follow from the local table having no data
> - unique constraints don't make sense
> - inde
I agree that it seems inappropriate to preserve order. That seems an
inappropriate imposition, inconsistent with what SQL does elsewhere.
If there is a natural sequence (e.g. - a value assigned by nextval()), that
offers a natural place to apply the usual order-imposing ORDER BY that we
are expec
On Tue, Oct 23, 2012 at 6:12 PM, Peter Eisentraut wrote:
> On 10/22/12 11:47 AM, Phil Sorber wrote:
> Also, it seems that about 75% of the patch is connection options processing.
> How about
> we get rid of all that and just have them specify a connection string? It
> would be a break
> with t
On Tue, Oct 30, 2012 at 5:25 PM, Josh Berkus wrote:
> On 10/29/12 6:40 AM, Chris Corbyn wrote:
>> What's the use case of this? It sounds like it will just create a
>> maintenance nightmare where some stuff you expect to lookup in in
>> postgresql.conf is actually hiding in the .auto file. Assumi
It seems not unusual for Linux distributions to supply libpq as part of a
separate package (whether via dpkg, which I think uses "ar" as the
archiver, or RPM, which uses cpio).
Possibly this is already provided on your system via some means akin to
those.
If, instead, you are keen on getting the
On Mon, Nov 5, 2012 at 12:19 PM, Robert Haas wrote:
> On Mon, Oct 29, 2012 at 4:31 PM, Jim Nasby wrote:
> > For whatever it's worth... we (and presumably others) still use londiste
> (or
> > Slony) as our upgrade path, so we could tolerate a cluster-wide setting.
> > We'd just set it when buildi
Preface: I think there's some great commentary here, and find myself
agreeing
pretty whole-heartedly.
On Tue, Nov 13, 2012 at 2:45 PM, Simon Riggs wrote:
> On 13 November 2012 17:38, Tom Lane wrote:
> > Simon Riggs writes:
> >> The most popular relational database in the world is Microsoft Acc
On Thu, Nov 15, 2012 at 2:53 PM, Darren Duncan
wrote:
> I still think the syntax of TRUNCATE FOR EACH ROW would be useful, but if
no one agrees...
I'm compelled to disagree.
What was useful about TRUNCATE in the first place was that it quickly
operated against the entire table.
If you want to c
of an up-front API change for something.
I suppose a next step might be to kick off gdb against the backend when
processing this.
--
output = ("cbbrowne" "@" "ca.afilias.info")
Christopher Browne
"Bother," said Pooh, "Eeyore, ready two photon tor
Dickson S. Guedes wrote:
2010/2/27 Tom Lane :
Buildfarm member caracara has been failing the last few days because of
this:
LOG: could not bind socket for statistics collector: Cannot assign requested
address
LOG: disabling statistics collector for lack of working socket
That code hasn't
On Thu, Apr 12, 2012 at 6:11 PM, Jay Levitt wrote:
> Rather than extend the CF app into a trivial-patch workflow app, it might be
> worth looking at integrating it with github.
There's a reluctance to require a proprietary component that could
disappear on us without notice.
The existence of git
ng this be
>> > more than a hack on seqscan, so I'm a bit nervous that this would turn
>> > into something bigger than a GSoC project.
>>
>> As Christopher Browne mentioned, for this sampling method, it is not
>> possible without scanning the whole data set.
On Tue, Apr 17, 2012 at 4:15 PM, Jay Levitt wrote:
> That's a great point. Both GitHub and git itself have no real concept of
> releases, and can't tell you when a commit made it in.
Those factors likely play together in this.
Git is a tool, not a workflow, and intentionally allows its users to
On Wed, Apr 18, 2012 at 1:08 PM, Josh Berkus wrote:
>> 3. Otherwise, they drift forever in the bleakness of space.
Seems to me that this line, is pretty close to being T-shirt-worthy.
> wontfix. We don't need a system to help us ignore bug reports; our
>> existing process handles that with admi
On Wed, Apr 18, 2012 at 1:48 PM, Magnus Hagander wrote:
> The problem I've found with most tools is that they work reasonably
> well if you let them control the entire workflow. But when you want to
> do things your own way, and it doesn't match up with what they were
> originally designed to do,
On Thu, Apr 19, 2012 at 10:49 AM, Magnus Hagander wrote:
> On Thu, Apr 19, 2012 at 16:45, Greg Sabino Mullane wrote:
>>
My github.com account currently has 4264 notifications in the inbox.
Almost all of those are spam, growing constantly. �Because of that, the
platform is current
On Fri, Apr 27, 2012 at 4:11 AM, Simon Riggs wrote:
> What I'm hoping to do is to build a basic prototype of logical
> replication using WAL translation, so we can inspect it to see what
> the downsides are. It's an extremely non-trivial problem and so I
> expect there to be mountains to climb. Th
On Tue, May 1, 2012 at 10:22 AM, Simon Riggs wrote:
> On Tue, May 1, 2012 at 3:08 PM, Robert Haas wrote:
>
>> We've previously discussed the possible desirability of extending
>> relations in larger increments, rather than one block at a time, for
>> performance reasons. I attempted to determine
On Wed, May 2, 2012 at 11:39 AM, Michael Nolan wrote:
> What is the use case for temporary tables on a hot standby server?
Simple...
We required a "hot standby" server in order to get improved reliability.
But we don't want it to sit there chewing power + money, unused.
We want to *use* it to
On Thu, May 10, 2012 at 12:55 PM, Josh Berkus wrote:
> On 5/10/12 9:44 AM, Peter Eisentraut wrote:
>> On tor, 2012-05-10 at 10:44 -0400, Bruce Momjian wrote:
>>> The big take-away is that the release notes are mostly for blame and
>>> to designate a go-to person for feature problems, not for givin
On Tue, May 22, 2012 at 4:35 PM, Stephen Frost wrote:
> * Josh Berkus (j...@agliodbs.com) wrote:
>> The local role is preferred, the same way we allow objects in the local
>> schema to overshadow objects in the global schema.
>
> I would think we'd want the exact opposite. I don't want my global
On Mon, May 28, 2012 at 11:39 AM, Dimitri Fontaine
wrote:
> Stephen Frost writes:
>> This is really where I was hoping to eventually get to with the logging
>> changes that have been discussed over the past couple of years. We need
>> to have a mechanism to allow logging to different places, bas
On Mon, May 28, 2012 at 1:45 PM, Robert Haas wrote:
> On May 28, 2012, at 11:57 AM, Christopher Browne wrote:
>> 2. Ask Syslog
>>
>> My favorite way to configure *my* PG instances (e.g. - those that I
>> use for testing) is for them to forward messages to syslog. Tha
On Sat, Jun 2, 2012 at 12:01 PM, Michael Nolan wrote:
> On 6/2/12, Tom Lane wrote:
>> Robert Haas writes:
>>> On the other hand, if we simply say "PostgreSQL computes the
>>> replication delay by subtracting the time at which the WAL was
>>> generated, as recorded on the master, from the time at
+1 indeed.
Very pleased to see this progression in the development team!
On Wed, Jun 13, 2012 at 7:28 AM, Andres Freund wrote:
> From: Andres Freund
>
> We decided to use low level functions to do the apply instead of producing sql
> statements containing the data (or using prepared statements) because both,
> the
> text conversion and the full executor overhead aren
On Thu, Jun 14, 2012 at 5:00 PM, Robert Haas wrote:
> On Thu, Jun 14, 2012 at 4:51 PM, Andres Freund wrote:
>> Lets sidetrack this till we have a tender agreement on how to handle DDL ;).
>> I
>> am aware of the issues with rollbacks, truncate et al...
>
> Agreed; I will write up my thoughts abo
On Mon, Jun 18, 2012 at 11:50 AM, Andres Freund wrote:
> Hi Simon,
>
> On Monday, June 18, 2012 05:35:40 PM Simon Riggs wrote:
>> On 13 June 2012 19:28, Andres Freund wrote:
>> > This adds a new configuration parameter multimaster_node_id which
>> > determines the id used for wal originating in o
On Tue, Jun 19, 2012 at 5:39 PM, Robert Haas wrote:
> On Tue, Jun 19, 2012 at 5:33 PM, Greg Smith wrote:
>> In January of 2011 Robert committed 7f242d880b5b5d9642675517466d31373961cf98
>> to try and compact the fsync queue when clients find it full. There's no
>> visible behavior change, just a
On Tue, Jun 19, 2012 at 5:46 PM, Robert Haas wrote:
>> Btw, what do you mean with "conflating" the stream? I don't really see that
>> being proposed.
>
> It seems to me that you are intent on using the WAL stream as the
> logical change stream. I think that's a bad design. Instead, you
> should
On Wed, Jun 20, 2012 at 11:50 AM, Andres Freund wrote:
> On Wednesday, June 20, 2012 05:34:42 PM Kevin Grittner wrote:
>> Simon Riggs wrote:
>> > This is not transaction metadata, it is WAL record metadata
>> > required for multi-master replication, see later point.
>
>> > We need to add informat
On Thu, Jun 28, 2012 at 3:03 PM, Josh Berkus wrote:
> 1. Databases can inadvertently get to the state where many tables need
> wraparound vacuuming at exactly the same time, especially if they have
> many "cold" data partition tables.
This suggests that this should be handled rather earlier, and
On Thu, Jul 5, 2012 at 11:59 AM, Tom Lane wrote:
> Alvaro Herrera writes:
>> Excerpts from Michael Glaesemann's message of jue jul 05 11:36:51 -0400 2012:
>>> If we're dumping objects (tables, views, functions, what-have-you) into
>>> separate files,
>>> each of these functions is a separate obj
On Thu, Jul 5, 2012 at 5:52 PM, Dimitri Fontaine wrote:
> Alvaro Herrera writes:
>> However I am also against what seems to be the flow. Normally, you
>> don't write overloaded plpgsql functions such as "equal". Case in
>> point, the equality functions in core have funny names like "int4eq" and
I wonder if maybe the nearest step towards "better bug tracker" is a more
readily referenceable mail archive.
Clearly, one of our "frictions" is searching for relevant messages, so
improved mail archive == lowered friction, no?
There's a very particular use case; people keep rueing that indexes
On Thu, Jul 19, 2012 at 4:29 PM, Joshua D. Drake wrote:
>
> On 07/19/2012 01:04 PM, Pavel Stehule wrote:
>>
>> I did a backport of temp_file_limit feature to 9.1, but when we tested
>> this patch, we found very restristrictive limit to 2GB.
>>
>> 2GB is nonsense, because this is session limit of t
On Sat, Apr 16, 2011 at 3:19 PM, Greg Smith wrote:
> Joshua Berkus wrote:
>>
>> Then you can say that politely and firmly with direct reference to the
>> problem, rather than making the submitter feel bad.
>>
>
> That's exactly what happened. And then you responded that it was possible
> to use a
On Mon, Apr 18, 2011 at 11:15 PM, Alex Hunsaker wrote:
> On Mon, Apr 18, 2011 at 19:50, Josh Berkus wrote:
>> You'll notice that this has been a complaint of veteran contributors as
>> well; WIP patches either get no review, or get reviewed as if they were
>> expected to be committable.
>
> I don
On Tue, Apr 19, 2011 at 12:22 PM, Robert Haas wrote:
> Yeah. I was wondering if anyone was gung-ho enough about this to
> implement some kind of library that both programs could draw on.
>
> It probably wouldn't be super-hard, if we could agree on a rough design.
It seems to me that the Mo Betta
On Thu, Apr 21, 2011 at 11:48 AM, Andres Freund wrote:
> One could argue that its causing bad PR for postgres. I have seen several
> parties planning to migrate away or not migrate to postgres because of
> performance evaluations they made. With 7.4, 8.0 and 8.2. In 2010.
Well evaluating based on
On Thu, Apr 21, 2011 at 11:05 AM, Robert Haas wrote:
> I agree. I am in favor of a shorter release cycle. But I think that
> a shorter release cycle won't work well if there is still four month
> long integration period at the end of each series of CommitFests. The
> problem is a bit circular h
On Thu, Apr 21, 2011 at 3:51 PM, Merlin Moncure wrote:
> On Thu, Apr 21, 2011 at 2:37 PM, Robert Haas wrote:
>> On Thu, Apr 21, 2011 at 2:13 PM, Tom Lane wrote:
>>> "Kevin Grittner" writes:
Josh Berkus wrote:
> ** question: if an SP is called by another SP, what is its
> transacti
On Sun, Apr 24, 2011 at 6:15 PM, Simon Riggs wrote:
> For large sets of low value data, it makes sense. Deleting all data,
> just simply because some of it might be damaged, is not the only
> option. IMHO deleting all the data is a surprising option that will
> cause many people to curse us. I don
On Mon, Apr 25, 2011 at 11:03 AM, Greg Stark wrote:
> If the tools become easy to run is it possible we cold get to the
> point where we do an indent run on every commit? This wold require a
> stable list of system symbols plus the tool would need to add any new
> symbols added by the patch.
Meth
On Mon, Apr 25, 2011 at 2:03 PM, Jesper Krogh wrote:
> On 2011-04-25 20:00, Leonardo Francalanci wrote:
>>> The amount of data loss on a big table will be <1% of the data
>>> loss caused by truncating the whole table.
>>
>> If that 1% is random (not time/transaction related), usually you'd
>> rath
On Tue, Apr 26, 2011 at 1:15 PM, Sim Zacks wrote:
> We have tried a similar approach, using plpythonu, by calling import pg and
> then creating a new connection to the database. This does give you an
> autonomous transaction, but not an asynchronous function.
> My use cases are mostly where the fu
On Fri, Apr 29, 2011 at 12:17 PM, Alvaro Herrera
wrote:
> Excerpts from David E. Wheeler's message of vie abr 29 13:04:35 -0300 2011:
>> On Apr 29, 2011, at 8:22 AM, Tom Lane wrote:
>>
>> > AFAICT the initial prompt is always "mysql> ", so they don't have to
>> > think hard about how many spaces t
On Tue, May 3, 2011 at 4:54 PM, Tom Lane wrote:
> Simon Riggs writes:
>> You're assuming that there are referential links *from* other tables
>> to the table with damage. In which case you would be correct. But of
>> course, if you needed that data for integrity you would never do that,
>> so the
2011/5/6 Krešimir Križanović :
> I don't know what to do with this backend interface. I would like to get a
> postmaster running and to connect to a data base with psql. However, when i
> try to start psql, it says that there is no postmaster running.
I would not assume that it is handled the same
On Fri, May 6, 2011 at 1:32 PM, Magnus Hagander wrote:
> On Fri, May 6, 2011 at 18:22, Euler Taveira de Oliveira
> wrote:
>> Em 06-05-2011 05:06, Magnus Hagander escreveu:
>>>
>>> On Fri, May 6, 2011 at 00:34, Josh Berkus
>>> wrote:
Hackers,
I've run into a couple of occasion
On Fri, May 6, 2011 at 2:32 PM, Greg Smith wrote:
> Christopher Browne wrote:
>>
>> I'm getting "paper cuts" quite a bit these days over the differences
>> between what different packaging systems decide to install. The one
>> *I* get notably bit on,
On Fri, May 6, 2011 at 3:01 PM, Gilberto Castillo Martínez
wrote:
> Josh,
>
> This would imply improvement in the terms of the U.S. embargo on Cuba.
>
> What would be real beneficial to all regional communities.
I wouldn't get overly optimistic about that - the purpose of this is a
bit less "swee
I quite agree with Peter's comments. Keeping this corporation as simple to
manage as possible is a considerably valuable feature. If we find we need
an "activity corporation," it won't be all that difficult to found that, and
it's worth noting that *that* organization would need to have a
substan
My example is of doing "self-discovery" to see if all needful database
components seem to be properly installed.
E.g. - the app needs pgcrypto, intarray, and a custom data type. The
install script can consequently inform the production folk either "looks
good", or, alternately, "seems problematic
On Mon, May 9, 2011 at 9:21 PM, Andrew Dunstan wrote:
>
>
> On 05/09/2011 08:20 PM, Bruce Momjian wrote:
>>
>> Tom Lane wrote:
>>>
>>> Peter Eisentraut writes:
On mån, 2011-04-25 at 14:35 -0500, Kevin Grittner wrote:
>
> (1) All the \d commands in psql should be implemented in
On Wed, May 18, 2011 at 12:15 PM, David E. Wheeler wrote:
> On May 18, 2011, at 10:30 AM, Dimitri Fontaine wrote:
>
>> The other problem is that the facility we need to provide the most is
>> binary distributions (think apt-get). Lots of site won't ever compile
>> stuff on their production server
On Wed, May 18, 2011 at 12:17 PM, Selena Deckelmann wrote:
> At the risk of starting an epic bikeshedding thread, I've attached a
> small patch that includes an example for both ipv4 and ipv6 localhost
> configuration.
My "bikeshedding" would be to ensure that the sample pg_hba.conf
includes some
On Wed, May 18, 2011 at 1:02 AM, Jaime Casanova wrote:
> So we the lock will be released at end of the session or when the
> UNLOCK DATABASE command is invoked, right?
> A question: why will we beign so rude by killing other sessions
> instead of avoid new connections and wait until the current se
On Thu, May 19, 2011 at 12:57 PM, Alvaro Herrera
wrote:
> Excerpts from Robert Haas's message of jue may 19 10:18:20 -0400 2011:
>> On Wed, May 18, 2011 at 7:11 PM, Alvaro Herrera
>> wrote:
>> >> 1. I suggested that this looks a lot like the controls of pg_hba.conf
>> >>
>> >> When our DBAs are
On Fri, May 27, 2011 at 9:24 PM, Peter Eisentraut wrote:
> On fre, 2011-05-27 at 13:55 -0400, Robert Haas wrote:
>> Also, I think it's about time we got ourselves some kind of bug
>> tracker. I have no idea how to make that work without breaking
>> workflow that works now, but a quick survey of m
On Mon, May 30, 2011 at 2:26 AM, Greg Stark wrote:
> On Sun, May 29, 2011 at 3:36 PM, Joe Abbate wrote:
>> Anyone interested in the tracker, please visit
>> http://wiki.postgresql.org/wiki/TrackerDiscussion and add your
>> feedback/input.
>
> I think this illustrates exactly what we *don't* want
On 2011-05-30 4:31 PM, "Peter Eisentraut" wrote:
>
> On sön, 2011-05-29 at 18:36 -0400, Joe Abbate wrote:
> > I've summarizes the main points made in the recent discussion and did
> > some minor additional research on the lists suggested by Peter and
> > Chris Browne. Anyone interested in the tra
On Tue, May 31, 2011 at 3:22 PM, Alvaro Herrera
wrote:
> Excerpts from Brendan Jurd's message of mar may 31 02:17:22 -0400 2011:
>> Hi folks,
>>
>> I was working on a little docs patch today, and when I tried to
>> `make`, openjade choked on an identifier in information_schema.sgml,
>> which is ve
On Wed, Jun 1, 2011 at 8:29 AM, Dave Page wrote:
> On Wed, Jun 1, 2011 at 12:27 PM, Andrew Dunstan wrote:
>>
>> The whole point of the revamp was that pg_listener was a major performance
>> bottleneck and needed to go, and without it being gone we would not have got
>> notification payloads.
>
>
On Thu, Jun 2, 2011 at 6:06 PM, Steve Crawford
wrote:
> On 06/01/2011 05:18 PM, Alvaro Herrera wrote:
>>
>> Excerpts from Jeff Davis's message of mié jun 01 19:57:40 -0400 2011:
>>>
>>> On Fri, 2011-05-27 at 16:43 -0400, Alvaro Herrera wrote:
Hi,
One of our customers is interes
On Fri, Jun 3, 2011 at 8:42 PM, Bruce Momjian wrote:
> Just to throw out a crazy idea, there has been talk of bug ids. What if
> a thread, made up of multiple message ids, was in fact the bug id, and
> the first message in the thread (ignoring month boundaries) was the
> definitive bug id, but an
On Sun, Jun 5, 2011 at 6:59 PM, Jeff Davis wrote:
> There might also be some middle ground, where its like the minimalist
> approach, but with a few very basic constructors and accessors. That
> would at least make it easier to test, but then to be actually useful
> (with index support, operators,
On Mon, Jun 6, 2011 at 5:13 PM, Simon Riggs wrote:
> The cost to us is a few days work and the benefit is a whole year's
> worth of increased performance for our user base, which has a hardware
> equivalent well into the millions of dollars.
I doubt that this is an accurate reflection of the cost
On Tue, Jun 7, 2011 at 5:40 PM, Andrew Dunstan wrote:
>
>
> On 06/07/2011 01:18 PM, Alex Hunsaker wrote:
>>
>> I don't suppose /dev/urandom blocks on OS X? Granted, I may have
>> missed something in translation with the macro fest that is perl...
>
>
> I wondered if we were possibly exhausting so
On Mon, Jun 13, 2011 at 4:08 PM, Aidan Van Dyk wrote:
> On Mon, Jun 13, 2011 at 3:54 PM, Dave Page wrote:
>
>> Yeah - MySQL is one of the ones I've been hacking on. It's hard to be
>> motivated if its going to need a complete rewrite within a year
>> though. I'll still have to work on it, as I've
On Wed, Jun 15, 2011 at 10:05 AM, Andrew Dunstan wrote:
> What I actually had in mind was rather different: an HBA mechanism based on
> appname. But on second thoughts maybe the protocol wouldn't support that.
Ah, a similar thought struck me.
Independent of this particular feature, it would be r
On Wed, Jun 15, 2011 at 10:05 AM, Andrew Dunstan wrote:
> What I actually had in mind was rather different: an HBA mechanism based on
> appname. But on second thoughts maybe the protocol wouldn't support that.
Ah, a similar thought struck me.
Independent of this particular feature, it would be r
On Wed, Jun 15, 2011 at 5:35 PM, Bruce Momjian wrote:
> This requires no new backend code. We could even _require_ the port
> number to be specified in pg_upgrade.
+1... That seems to have lots of nice properties.
--
When confronted by a difficult problem, solve it by reducing it to the
questi
On Wed, Jun 15, 2011 at 8:54 PM, Josh Berkus wrote:
> I've trolled this list, and I think I added in all patches which were
> submitted here but not on the commitfest app. Can someone double-check
> for me?
There's a "read and heed" that's appropriate here...
As hard as we may try, if you imag
On Thu, Jun 16, 2011 at 1:48 PM, Bruce Momjian wrote:
> Tom Lane wrote:
>> "Ross J. Reedstrom" writes:
>> > As an operations guy, the idea of an upgrade using a random,
>> > non-repeatable port selection gives me the hebejeebees.
>>
>> Yeah, I agree. The latest version of the patch doesn't appea
On Fri, Jun 24, 2011 at 5:15 PM, Greg Smith wrote:
> -All of these other ways to analyze of the contributors would be much easier
> to maintain. A little "Author:" decoration to that section of each commit
> would probably be welcome too.
I think you're quite right, that "mining" the commit logs
On Fri, Jun 24, 2011 at 6:47 PM, Greg Smith wrote:
> On 06/24/2011 01:42 PM, Robert Haas wrote:
>> I am not inclined to try to track sponsors in the commit message at
>> all.
>
> I was not suggesting that information be part of the commit. We've worked
> out a reasonable initial process for the p
On Mon, Jun 27, 2011 at 1:49 PM, David E. Wheeler wrote:
> Hackers,
>
> I'm curious about behavior such as this:
>
> bric=# select generate_series('2011-05-31'::timestamp ,
> '2012-04-01'::timestamp, '1 month');
> generate_series
> -
> 2011-05-31 00:00:00
> 2011-06-30 00:0
On Mon, Jun 27, 2011 at 2:36 PM, Steve Crawford
wrote:
> On 06/27/2011 10:56 AM, David E. Wheeler wrote:
>>
>> On Jun 27, 2011, at 10:54 AM, Steve Crawford wrote:
>>
>>> That's just how intervals that represent varying periods of time work.
>>> You would need to write your own. But a series of end
On Fri, Mar 11, 2011 at 12:37 PM, Jeff Davis wrote:
> Right now it's #3, and I lean pretty strongly toward keeping it. Without
> #3, people will get confused when fairly simple operations fail in a
> data-dependent way (at runtime). With #3, people will run into problems
> only in situations where
On Fri, Mar 11, 2011 at 12:50 PM, Bruce Momjian wrote:
> It has bothered me that many of our time routines use special magic
> constants for time values, e.g. 24, 12, 60, etc.
>
> The attached patch changes these magic constants to macros to clarify
> the code. I would like to apply this for 9.1
On Sat, Mar 12, 2011 at 8:59 AM, Bruce Momjian wrote:
> Dave Page wrote:
>> On 3/12/11, Tom Lane wrote:
>> > Bruce Momjian writes:
>> >> People are confused about what template0 is for, so I created the
>> >> attached one-line patch to add a database comment to template0. No
>> >> initdb, I assu
On Sat, Mar 12, 2011 at 9:14 AM, Bruce Momjian wrote:
> I like that. Perhaps "unmodified template database'?
"why" tends to be more important than "what", particularly to a
confused DBA who's trying to figure out "why do they have all these
extra databases???"
Perhaps...
"backup template databa
On Mon, Mar 28, 2011 at 10:19 AM, Shridhar Polas
wrote:
> Hi,
> Is there a way to create triggers on system catalog tables like
> pg_class, pg_attribute etc...?
No, this isn't supported, and, since the normal alterations of the
schema involve manipulating these tables, such an addition would be
f
On Tue, Mar 29, 2011 at 2:48 PM, Josh Berkus wrote:
>> Writing such long emails seems to be just filibustering to me. I doubt
>> anyone has read and considered every word, there are just too many. A
>> form of disrespect.
>
> Simon, Robert has been nothing but respectful to you. You can't accuse
On Wed, Mar 30, 2011 at 9:59 AM, David Fetter wrote:
> On Tue, Mar 29, 2011 at 08:21:04PM -0400, Robert Haas wrote:
>> On Mar 29, 2011, at 2:17 PM, Christopher Browne wrote:
>> > A proposal to adding triggers to system catalog tables won't be
>> > terribly popula
An advantage to this uri form is that it allows applications to be
configured uniformly - I do not need to ask "is this using libpq, needing
one sort of configuration, or Java, needing another?"
Rather, I may say, "here is a uri I may use with any of my applications"
On Fri, Apr 1, 2011 at 12:43 PM, Joshua D. Drake wrote:
> On Fri, 2011-04-01 at 08:13 -0400, Andrew Dunstan wrote:
>
>> >> That said, I do support adding this in the future, if only to keep up
>> >> with the Jones'.
>> > So are the ones out there *already* even compatible, before we start
>> > add
On Mon, Apr 4, 2011 at 1:26 PM, Susanne Ebrecht wrote:
> Anyway, I figured out there is another argument for XML:
>
> My information is that DocBook 5.0 won't support SGML anymore.
>
> Which means - sooner or later a reaction is needed.
Yes, indeed.
I don't think that during the 9.1 alpha phase
On Mon, Apr 11, 2011 at 7:33 AM, Nick Raj wrote:
> Can anyone know how to define global variable in plpgsql?
I expect you should consult the manual page on the command CREATE
TABLE. That's what would be the nearest SQL equivalent to a "global
variable."
http://www.postgresql.org/docs/9.0/static
On Thu, Nov 14, 2013 at 5:41 AM, Sameer Thakur wrote:
> So i think -g option is failing
Right you are.
I was missing a "g:" in the getopt_long() call.
Attached is a revised patch that handles that.
And it behaves better:
postgres@cbbrowne ~/p/s/b/scripts> ./createuser -g purge_role -U
postgres
On Fri, Nov 15, 2013 at 3:14 PM, Peter Eisentraut wrote:
> On 11/14/13, 4:35 PM, Christopher Browne wrote:> On Thu, Nov 14, 2013 at
> 5:41 AM, Sameer Thakur wrote:
>>> So i think -g option is failing
>>
>> Right you are.
>>
>> I was missing a "g:&
On Mon, Nov 18, 2013 at 1:01 AM, Amit Kapila wrote:
> On Sat, Nov 16, 2013 at 4:57 AM, Christopher Browne
> wrote:
> Few comments:
>
> 1.
> + -g
> + --roles
>
> All other options which require argument are of form:
> -c class="parameter"&
On Tue, Nov 19, 2013 at 11:54 PM, Amit Kapila wrote:
> On further tests, I found inconsistency in behavior when some special
> characters are used in role names.
>
> 1. Test for role name containing quotes
> a. In psql, create a role containing quotes in role name.
>create role amitk in ro
Wait, that doesn't work if more than one role is added, as they get
merged together by the quoting.
A somewhat ugly amount of quoting can be done at the shell level to
induce double quotes.
$ createuser -g "\"test_rol'e_3\"" usequoted3
I note that similar (with not quite identical behaviour) iss
On Fri, Nov 8, 2013 at 10:33 AM, Alvaro Herrera
wrote:
> Hello,
>
> Attached you can find a very-much-WIP patch to add CREATE info support
> for event triggers (normalized commands). This patch builds mainly on
> two things:
>
> 1. Dimitri's "DDL rewrite" patch he submitted way back, in
>http
On Wed, Dec 11, 2013 at 7:53 AM, Robert Haas wrote:
> On Tue, Dec 10, 2013 at 9:55 AM, Amit Kapila wrote:
>> On Tue, Dec 10, 2013 at 12:20 AM, Robert Haas wrote:
>>> On Sat, Dec 7, 2013 at 11:39 PM, Amit Kapila
>>> wrote:
On Fri, Dec 6, 2013 at 10:31 AM, Peter Eisentraut wrote:
>
>>>
On 11 May 2016 at 12:58, Josh berkus wrote:
> Together with that, automated substitution of materialized views for
> query clauses.
>
> Also: optimizing for new hardware, like persistent memory.
I recently saw some material in ACM SIGOPS on tuning filesystems to play
better with some of the new
101 - 200 of 483 matches
Mail list logo
