On 20 Nov 2002, Neil Conway wrote:
> However, the FreeBSD box I'm playing with isn't mine, so I'm not too
> keen to change sysctls (well, that and I don't have root :-) ). Would
> a kind BSD user confirm that:
>
> (a) the sysctls above *can* be used to change kernel shared
> m
On Tue, 7 Jan 2003, Dan Langille wrote:
> On 7 Jan 2003 at 16:25, mlw wrote:
>
> > I think banner ads that build on PostgreSQL's message is a good thing.
> > A RedHat ad, maybe IBM, etc. Companies with a related purpose to the
> > PostgreSQL mission will offset some of the cost and help build the
On Tue, 4 Feb 2003, Neil Conway wrote:
> Spencer's implementation is outperformed by some other RE engines,
> notably PCRE (www.pcre.org). But switching to another engine might
> impose backward-compatibility problems, in terms of the details of the
> RE syntax.
It would be a delight to be able t
On Wed, 5 Feb 2003, Tom Lane wrote:
> 1. There are a couple of minor incompatibilities between the "advanced"
> regex syntax implemented by this package and the syntax handled by our
> old code; in particular, backslash is now a special character within
> bracket expressions. It seems to me that
On Fri, 28 Mar 2003, Tom Lane wrote:
> It seems to me that it'd be fairly easy to make BEGIN cause only
> a local state change in the backend; the actual transaction need not
> start until the first subsequent command is received.
[snip]
> In a very real sense, the transaction snapshot defines "wh
On Fri, 4 Apr 2003, Tom Lane wrote:
> We should also take a look at Apache's rotator to see if there's any need
> to reinvent the wheel at all. I have not seen it, am not even sure what
> it's written in...
It's written in 140 lines of C (blank lines and all), and has been very
solid in my exper
ttings on both client and
server to cover all needs, along these lines:
> Date: Tue, 7 Jan 2003 16:07:58 -0500 (EST)
> From: Bruce Momjian <[EMAIL PROTECTED]>
> To: Peter Eisentraut <[EMAIL PROTECTED]>
> Cc: Jon Jensen <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
>
On Thu, 19 Jun 2003, Christopher Kings-Lynne wrote:
> Does anyone care about contrib/reindexdb anymore?
I would've found it handy, but didn't know about it and wrote my own in
Perl. Inside a transaction it drops the index then rebuilds it using what
it gets from pg_get_indexdef(), and it looks at
On Tue, 12 Aug 2003, Tom Lane wrote:
> I have just finished running some experiments that compared a series of
> INSERTs issued via PQexec() versus preparing an INSERT command and then
> issuing new-FE-protocol Bind and Execute commands against the prepared
> statement. With a test case like the
On Thu, 21 Aug 2003, Andrew Dunstan wrote:
> Linux kernel version 2.4.* has poor default memory overcommit behavior,
> which can result in the postmaster being killed by the kernel due to
> memory demands by another process if the system runs out of memory. To
> avoid this situation, run postgr
On Thu, 28 Aug 2003, Andrew Dunstan wrote:
> What is the state of things regarding having to use massive strings of
> quotes like this (taken from the 7.3 docs)?:
>
> a_output := a_output || '' if v_'' ||
> referrer_keys.kind || '' like ''
> || referrer_keys.key_string || '''
On Sat, 30 Aug 2003, Bruce Momjian wrote:
> > >I was thinking the most natural thing would be to use something similar to
> > >COPY's stdin quoting:
> > >
> > >CREATE FUNCTION bob() RETURNS INTEGER AS stdin LANGUAGE 'plpgsql';
> > >BEGIN
> > > ...
> > >END;
> > >\.
>
> Is there a TODO here? Th
On Thu, 4 Sep 2003, Dann Corbit wrote:
> > Use the Cygwin tools.
>
> Cygwin requires a license for commercial use.
It does? I don't see it:
http://cygwin.com/licensing.html
Jon
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Thu, 4 Sep 2003, Dann Corbit wrote:
> Did you read this:
> "This means that unless you modify the tools so that compiled
> executables do not make use of the Cygwin library, your compiled
> programs will also have to be free software distributed under the GPL
> with source code available to all
> >On Wed, Sep 10, 2003 at 07:04:13PM +0200, Andreas Pflug wrote:
> >
> >>>I assume we never came to a final conclusion on how to do CREATE
> >>>FUNCTION without double-quoting.
> >
> >>Many discussions, but no final conclusion in sight, it seems. That
> >>\beginliteral stuff is psql centric, wher
On Wed, 10 Sep 2003, Alvaro Herrera wrote:
> On Wed, Sep 10, 2003 at 10:35:18PM +0200, Andreas Pflug wrote:
>
> > I never agreed that a client solution would be satisfying. While
> > frontends might try to hide some uglyness of the syntax to the user for
> > single functions, editing large scri
On Thu, 10 Sep 2003, Doug McNaught wrote:
> But Perl/DBI does escaping for you, so all you'd have to do is:
>
> $sth = $dbh->prepare
>("CREATE FUNCTION foo(x text) RETURNS text AS ? LANGUAGE 'plpgsql'");
> $sth->execute($function_body);
>
> where $function_body is the unescaped form of the f
On Thu, 11 Sep 2003, Tom Lane wrote:
> People seem to be assuming that this feature needs to be impervious to
> whitespace and being adjacent to other things. I believe we could make
> it a good deal more robust if both the opening and closing markers
> (whatever they are) are required to stand a
On Thu, 11 Sep 2003, Bruce Momjian wrote:
> > I would definitely like to see us adopt a proposal that is like
> > here-documents to the extent that there's a family of possible
> > terminator markers and not only one. But we'll have to adjust the
> > syntax a little bit. If you don't like $$FOO,
On Thu, 11 Sep 2003, Tom Lane wrote:
> It is possible that we could allow the start marker to be not at the
> beginning of its line, which would create structures very very close
> to shell here-documents:
>
> CREATE FUNCTION foo() RETURNS int AS $$FUNCTION
> ... text here ...
>
On Fri, 12 Sep 2003, Tom Lane wrote:
> I'm currently leaning to an idea that was suggested yesterday by (I
> think) Andreas: let the quote start marker be a token of the form
> dollarsign zero-or-more-letters dollarsign
> and let the quote body extend to the next occurrence of the identical
On Mon, 15 Sep 2003, Tom Lane wrote:
> Hm, "dollar quoting" doesn't sound too bad. I could go with that,
> unless someone has a better idea?
I don't mind "dollar quoting". How about "block quoting"? That describes
what it's used for, rather than what it looks like.
Jon
---
On Sat, 13 Sep 2003, Miko O'Sullivan wrote:
> [EMAIL PROTECTED] (Jon Jensen) wrote in message news:<[EMAIL PROTECTED]>...
> > INSERT INTO sometable (5, <<\.
> > a
> > very long
> > string
> > \.
> > );
>
>
> I'm delighted to
On Mon, 15 Sep 2003, Tom Lane wrote:
> >> In Perl, the rule for here docs is NOT "it starts immediately after
> >> the definition of the terminator" (as in your example). The rule is
> >> "it starts on the first line after the end of the command in which the
> >> terminator appears". There's a v
an have a \X command that uses
expanded mode only for non-slash output.
What do others think about this?
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
---(end of broadcast)---
TIP 9: the planner will ignore your desire t
.
It seems that far and away the most common use of this database will be as
the default database to connect to with any of the client apps. Thus Tom's
suggestion of "default" makes the most sense to me.
Jon
--
Jon Jensen
End Point Corporation
http:
On Thu, 18 Mar 2004, Josh Berkus wrote:
> Jeremy handed me an interesting feature proposal at last night's SFPUG
> meeting.
>
> PG authentication methods ought to have drop-downs to other authentication
> methods, in the same manner as SSH and PAM.
>
> The idea would be this, if you had the fo
On Thu, 18 Mar 2004, Bruno Wolff III wrote:
> On Thu, Mar 18, 2004 at 22:58:46 +0000, Jon Jensen <[EMAIL PROTECTED]> wrote:
> >
> > Is there some other way to do what I'm looking for here without the
> > authentication method fallthrough Josh proposes?
>
On Wed, 24 Mar 2004, Christopher Kings-Lynne wrote:
> > I don't mind if it's on by default; just thinking that some people might
> > appreciate a way to turn it off. "-X disable-dollar-quoting" sounds
> > fine.
>
> Does it _have_ to be dollars? Other languages call this feature
> 'heretext' II
On Wed, 28 Apr 2004, Christopher Kings-Lynne wrote:
> >>Seriously - I'd like to raise my voice in favor of installing plpgsql
> >>in template1 by default. I haven't heard any good reason not to (nor
> >>even a bad reason).
>
> It has to work with older dumps that will try to recreate pl/pgsql
>
On Thu, 20 May 2004, Neil Conway wrote:
> Personally I'd prefer the entire diff to be attached to each -committers
> mail, which would circumvent this problem. Would others find that
> objectionable?
I would really like that. It'd be a lot easier to see what's going on.
Jon
--
On Fri, 28 May 2004, Christopher Kings-Lynne wrote:
> > I've encountered a situation where I'd like to store some information
> > about the database when I do a pg_dump. For instance, the timestamp of
> > the dump. And some other information that I pull from the database.
>
> I think every dump
On Fri, 27 Aug 2004, Greg Sabino Mullane wrote:
> 3. I'd like to rearrange the ORDER BY on some objects to show
> user-created objects before system ones. Currently, if I create
> a new function and do a \df, I have to wade through all the
> system functions in the pg_catalog schema before seeing
On Fri, 26 Sep 2003, Tom Lane wrote:
> I was chewing this over with Bruce on the phone just now, and we refined
> the idea a little. Some errors (primarily those detected inside the
> datatype input procedures) can be clearly traced to a specific column,
> whereas others (such as too many fields
On Tue, 14 Oct 2003, Bruce Momjian wrote:
> I knew you were adding --help-config, but I didn't realize the extent of
> the "features". The commit message is:
>
> revision 1.1
> date: 2003/07/04 16:41:21; author: tgl; state: Exp;
> Add --help-config facility to dump informatio
On Tue, 14 Oct 2003, Rod Taylor wrote:
> > > I wouldn't want the whole diff on the mail, but a link to the relevant
> > > diffs in cvsweb would be most useful (one for each changed file -- not ideal,
> > > but much better than nothing). You're not the first one to suggest it ...
> >
> > I agree,
On Wed, 22 Oct 2003, scott.marlowe wrote:
> > > That said, perhaps the TODO for changing LIMIT / OFFSET to be expression
> > > based should also mention bumping them to int8.
> >
> > Can't get excited about it ... this would slow down the normal use of
> > the facility for what seems a completely
On Tue, 28 Oct 2003, Tom Lane wrote:
> Note that tables, indexes, views and sequences relations in the
> 'pg_catalog' namespace are excluded even though they are in the
> current search path. I found not doing this produced annoying
> behaviour when expanding names beginnin
On Mon, 17 Nov 2003, Neil Conway wrote:
> I'd like to add a new column to pg_attribute that specifies the
> attribute's "logical position" within its relation. The idea here is
> to separate the logical order of the columns in a relation from the
> on-disk storage of the relation's tuples. This al
On Tue, 16 Dec 2003, Alvaro Herrera wrote:
> BTW, what happened to the $QUOTE$ quoting idea? Was it applied, or
> even developed?
I believe it's still on the to-do list, but was pushed off until 7.5 or
whenever it gets done.
Jon
---(end of broadcast)
On Tue, 16 Dec 2003, Jan Wieck wrote:
> If you want to prevent "accidential" access, start postmaster on a
> non-standard port.
That seems like an unfriendly thing to do. You'd have to check to see what
port is "standard" for this particular installation, and pick something
else. You may choos
On Tue, 16 Dec 2003, scott.marlowe wrote:
> > > If you want to prevent "accidential" access, start postmaster on a
> > > non-standard port.
> >
> > That seems like an unfriendly thing to do. You'd have to check to see what
> > port is "standard" for this particular installation, and pick someth
On Tue, 6 Jan 2004, Andrew Dunstan wrote:
> >Also, I would like to see some kind of session identifier that is more
> >unique than pid, which wraps around. Ideally we could have 10{pid},
> >then then the pid wraps around, 20{pid), or something like that.
>
> This requires some thought. ISTM it w
On Sat, 10 Jan 2004, Tom Lane wrote:
> ISTM there are three fundamental problems with \d and friends:
>
> 1. Some people have a hard time remembering the commands.
> 2. Some people aren't using psql.
> 3. psql keeps breaking across backend versions because the
> needed
On Thu, 5 Feb 2004, Andrew Dunstan wrote:
> What has become of the "dollar quoting" mechanism that we had so much
> discussion about back in August/September?
>
> IIRC, a consensus was reached on the actual format of the quote
> delimiters (either $$ or $identifier$), and Tom had a proof of con
On Tue, 24 Feb 2004, Stephen wrote:
> It came to my mind that what if there could be a mechanism in place to allow
> overwriting portions of the same row *whenever possible* instead of creating
> a new row as MVCC would require.
How would you do a rollback if an error occurred mid-query? How woul
On Thu, 18 Mar 2004, Richard Huxton wrote:
> On Thursday 18 March 2004 10:18, Fabien COELHO wrote:
> > On Wed, 17 Mar 2004, Tom Lane wrote:
>
> > > though I'd be worried about the portability price paid to have one. Or
> > > are you concerned about whether a GUI could invoke it? I don't see why
, but OTOH I trained myself not to do \d there very often
either, since it was so slow and failed so often, so that may be
coincidence. :)
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ...
g hourly or daily, to keep the
DNS lookups from getting too stale.
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ...
---(end of broadcast)---
TI
ity of multiple IP addresses coming back.
But I agree that complicating this simple feature is overkill. The
database is not a firewall, and doesn't have a firewall's speed due to
connection overhead anyway.
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
suggested yesterday, but others didn't like it and the
possibility of using /etc/hosts or a name server on the local network to
mitigate speed concerns makes me think they're right.
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
l.conf, then very little output goes
to /var/log/pgsql, usually of an important nature like "stopped" or
"started" at a certain date. I normally change that first thing after a
new install.
Just wondering.
Thanks,
Jon
--
Jon Jensen
End Point Corporation
http:
ting to
> stdout, for example - all IO should be forbidden).
That makes sense. Allowing "rand" would be nice too.
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
Software development with Interchange, Perl, PostgreSQL, Apache, Linux, ...
---
luding :base_math would bring it back.
> What we should do, however, is disallow is calling srand, since pg goes
> to quite a bit of trouble to seed the PRNG.
That sounds reasonable.
Jon
--
Jon Jensen
End Point Corporation
http://www.endpoint.com/
Software development with I
y, or (3) you'll have
to go back to the drawing board if it's an obvious loss.
This problem's been talked about a lot, but seeing some code and metrics
from someone with a personal interest in solving it would really be
progress IMHO.
Jon
--
Jon Jensen
End Point Corporation
http://
55 matches
Mail list logo
