On Tue, Nov 14, 2000 at 03:05:04PM -0500, Tom Lane wrote:
I think that in the last discussion of shared memory key assignment,
we had come up with a plan for detecting key collisions directly instead
of hoping they wouldn't happen. I don't have time to pursue this right
now, but according
It's a shell thing: Vince is running csh (or a derivative thereof)
while Tom (and I) are running some sort of Bourne derived shell.
Vince, try:
psql -\?
Which works more universally.
Ross
On Sun, Nov 19, 2000 at 02:44:01PM -0500, Tom Lane wrote:
Vince Vielhaber [EMAIL PROTECTED] writes:
On Mon, Nov 20, 2000 at 06:52:20PM +0200, Hannu Krosing wrote:
Dumping constraints in human-readable form (instead of CREATE CONSTRAIN
TRIGGER) would also be great.
In fact, IMHO, this would be a great place to start: we'd all love the
fuctionality, it'd have you examining almost all the
Uh, Don?
Not all the world's a web page, you know. Thatkind of thinking is _so_
mid 90's ;-) Dedicated apps that talk directly the user seem to be making
a comeback, due to a number of factors. They can have much cleaner user
interfaces, for example.
Which brings us back around to the point of
On Sat, Dec 02, 2000 at 11:31:37AM -0800, Don Baccus wrote:
At 05:42 PM 12/2/00 +0100, Peter Eisentraut wrote:
Don Baccus writes:
Exactly what is PostgreSQL, Inc doing in this area?
Good question... See http://www.erserver.com/.
snip
Boy, I can just imagine the uproar this
On Sat, Dec 02, 2000 at 03:47:19PM -0800, Adam Haberlach wrote:
Where's the damn core code? I've seen a number of examples already of
people asking about remote access/replication function, with an eye
toward implementing it, and being told "PostgreSQL, Inc. is working
on that". It's
On Sat, Nov 04, 2000 at 10:09:16PM -0800, Vadim Mikheev wrote:
I think that to handle locations we could symlink catalogs - ln -s
path_to_database_in_some_location .../base/DatabaseOid
But that's a kludge. We ought to discourage people from messing with the
storage internals.
On Sun, Dec 03, 2000 at 08:49:09PM -0400, The Hermit Hacker wrote:
On Sun, 3 Dec 2000, Hannu Krosing wrote:
IIRC, this thread woke up on someone complaining about PostgreSQl inc
promising
to release some code for replication in mid-october and asking for
confirmation
that this
On Sun, Dec 03, 2000 at 08:53:08PM -0400, The Hermit Hacker wrote:
On Sun, 3 Dec 2000, Gary MacDougall wrote:
If you write a program which stands on its own, takes no work from
uncompensated parties, then you have the unambiguous right to do what
ever you want.
Thats a given.
On Sun, Dec 10, 2000 at 04:08:58PM -0800, Nathan Myers wrote:
On Thu, Dec 07, 2000 at 02:28:28PM -0500, Tom Lane wrote:
Given all that, here is a proposed spec for the header:
...
Comments?
(I have also suggested, in private mail, that the "header length"
field should be the length
, except for
the procedural languages on the server itself. Debian has package naming
policies for library and development packages. Libraries are named libfoo,
while development packages (usually header files) are foo-dev.
Ross
--
Ross J. Reedstrom, Ph.D., [EMAIL PROTECTED]
NSBRI Research Scientist
On Thu, Dec 14, 2000 at 01:16:20PM +, Hannu Krosing wrote:
The Hermit Hacker wrote:
snip
vadim, for v7.2, is planning on re-writing the storage manager to do
proper overwriting of deleted space, which will reduce the requirement for
vacuum to almost never ...
I hope that he does
Hey hackers -
I'm having a bit of trouble with creating a new bootstrap system
table. That is, one that is created during initdb via 'create bootstrap'
in the PKI file.
I realize that for this sort of system table, I need to add tuples via
bootstrap DATA statements to pg_class.h,
On Fri, Jan 05, 2001 at 06:25:38PM -0500, Tom Lane wrote:
Still, it sure looks like 'create bootstrap' should cause mdcreate()
to be called, so I'm not sure why you'd see the file not get created
at all. Have you tried tracing through it with a debugger?
Do you really need the thing to
On Sat, Jan 06, 2001 at 03:50:03AM +0100, Peter Eisentraut wrote:
Ross J. Reedstrom writes:
Do you really need the thing to be a bootstrap table, and not a plain
system table?
Yup, 'cause it's going to store the schema info, including the system
schema. I forsee it needing
On Wed, Jan 17, 2001 at 05:49:36PM -0500, Bruce Momjian wrote:
Wow, this looks great, and it worked the first time too. I will commit
if no one makes objects.
I object. The code displays oids and tablenames or relnames. Oid is just
the initial, default filename for tables, and may change to
On Mon, Jan 22, 2001 at 12:18:54PM -0500, Joel Burton wrote:
On Mon, 22 Jan 2001, Zeugswetter Andreas SB wrote:
Is anyone looking at doing this? Is this purely a MySQL-ism, or is it
something that everyone else has except us?
We should not only support access to all db's under
On Mon, Jan 22, 2001 at 12:41:38PM -0500, Joel Burton wrote:
On Mon, 22 Jan 2001, Ross J. Reedstrom wrote:
And this case can be handled within one database by having multiple
schema, one for each package. It's not there yet, but it's a simpler
solution than the generic solution
It got bounced to Constantin. I'm not sure if it's made it in, there.
I'll ping him and see if he needs a new patch.
Ross
On Wed, Jan 24, 2001 at 08:49:13AM -0500, Bruce Momjian wrote:
Ross, this looks very good. What happened to it?
Here's a patch to clean up some issues with the
?
If that makes it go away, I'd say it pretty well points straight into
the Solaris kernel.
Ross
--
Ross J. Reedstrom, Ph.D., [EMAIL PROTECTED]
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005
On Fri, Jan 26, 2001 at 03:18:13PM -0500, Bruce Momjian wrote:
The 'tmpwatch' program on Red Hat will remove the /tmp/.s.PGSQL.5432.lock
file after the server has run 6 days. This will be a problem.
We could touch (open) the file once every time the ServerLoop() runs
around. It's not
On Fri, Jan 26, 2001 at 11:55:16PM -0500, Bruce Momjian wrote:
I said:
Yes, there are lots of systems that will clean /tmp --- and since the
lock file is an ordinary file (not a socket) pretty much any tmp-cleaner
is going to decide to remove it. I think that I had intended to insert
On Mon, Feb 05, 2001 at 09:17:45PM -0500, Tom Lane wrote:
Yes, on looking at it I see that someone broke PQoidStatus() in 7.0.
If you want to fix your copy, the patch (line numbers are for current
CVS) is
Index: fe-exec.c
On Tue, Feb 06, 2001 at 01:21:00PM -0500, Bruce Momjian wrote:
What if len 23?
mea culpa. Must go eat lunch. No sugar to brain. (and no, I didn't put
the original error in :-)
Ross
On Tue, Feb 06, 2001 at 07:08:20PM -0500, Tom Lane wrote:
[EMAIL PROTECTED] (Nathan Myers) writes:
Thus, the original code is OK, except probably the literal "23"
in place of what should be a meaningful symbolic constant, or
(at least!) sizeof(buf) - 1.
No, the original code is NOT ok.
On Tue, Feb 06, 2001 at 06:17:46PM -0600, Ross J. Reedstrom wrote:
Seems it's a non-portable behavior:
The strncpy() function is similar, except that not more
than n bytes of src are copied. Thus, if there is no null
byte among the first n bytes of src, the result
On Wed, Feb 07, 2001 at 01:34:58PM -0500, Tom Lane wrote:
I thought I'd tried pgAccess back in the dim past with success, but as
of current sources it fails on HPUX 10.20 and Tcl 8.3.2:
SNIP problem with dynamic load and Tcl
And the reason for *that* is that Tcl doesn't pass the
On Fri, Feb 09, 2001 at 12:04:08PM -0500, Bruce Momjian wrote:
I see the new PL/PgSQL command:
GET DIAGNOSTICS
This seems like a poorly-worded command to me. It is meant to return
the number of rows affected by a previous query, right?
Among other things, eventually. You get to
On Sun, Dec 17, 2000 at 06:03:34PM -0500, Michael Richards wrote:
Having written this tool which is at least the basis for a complete table
data verification program (it's written in c++) I'm wondering if there is
any chance of having it pointed to, linked to or otherwise made available?
On Thu, Mar 15, 2001 at 09:34:04AM -0800, G. Anthony Reina wrote:
Ken Hirsch wrote:
So rtrim("center_out_opto", "_opto") returns
"center_ou"
because "u" is not in the set {o, p, t, _} but all the characters after it
are.
rtrim("center_out_opto", "pot_") will produce the same
On Thu, Mar 15, 2001 at 01:18:57PM -0500, Tom Lane wrote:
"Ross J. Reedstrom" [EMAIL PROTECTED] writes:
Is there a way to just remove the "_opto" from the end of the string?
If you have exactly one known string to (optionally) remove, this works
(and even works if t
On Thu, Nov 19, 2009 at 05:15:05PM -0700, u235sentinel wrote:
Does anyone have a link for pl/ruby? I found a link under the postgres
documentation and found a web site from there talking about the code.
However when I clicked on the link to download it I noticed ftp wouldn't
respond on
On Tue, Nov 24, 2009 at 03:12:43PM +0900, KaiGai Kohei wrote:
Itagaki Takahiro wrote:
* CREATE TABLE tbl (col integer AS SECURITY_CONTEXT = '...')
Is the syntax AS SECURITY_CONTEXT natural in English?
We need to put a reserved token, such as AS, prior to the SECURITY_CONTEXT
to avoid
On Mon, Dec 07, 2009 at 10:49:13AM +, Dave Page wrote:
On behalf of the core team, I'm pleased to announce that the
Congratulations!
+1 Congrats to you all, and thanks for the contributions, both past and
future.
As an aside, this sort of thing is one of the best signs to an external
On Wed, Jan 13, 2010 at 05:03:33PM -0500, Robert Haas wrote:
On Wed, Jan 13, 2010 at 4:47 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Spelling out primary key would seem to be more in keeping with existing
entries in that column, eg we have not null not NN.
I think this is a sensible
On Mon, Jan 25, 2010 at 06:06:53PM +0200, Alastair Bell Turner wrote:
..
without having to add a switch to their command lines. It's not going
to have anything to say to experienced psql users anyway so it would
probably not bug anyone enough to turn it off.
I would so use this feature going
On Mon, Jan 25, 2010 at 10:49:55AM -0600, Ross J. Reedstrom wrote:
On Mon, Jan 25, 2010 at 06:06:53PM +0200, Alastair Bell Turner wrote:
..
without having to add a switch to their command lines. It's not going
to have anything to say to experienced psql users anyway so it would
probably
On Wed, Feb 10, 2010 at 07:01:19PM +0200, Priit Laes wrote:
It might avoid the 'UU, I forgot to enable python support.',
after you have waited a while for the build to finish...
+1 from me, for that very reason!
Ross
--
Ross Reedstrom, Ph.D.
On Sun, Feb 14, 2010 at 05:08:05PM +0100, Yeb Havinga wrote:
Little, Douglas wrote:
Hi,
Is there a PG command or fuction that will return table ddl?
If you just want the definition,in psql type \d tablename.
To dump ddl the pg_dump with proper arguments can dump just the ddl of a
On Wed, Mar 31, 2010 at 10:34:41PM -0400, Bruce Momjian wrote:
Matthew Altus wrote:
Hey,
After dealing with a production fault and having to rollback all the time,
I
kept typing a different word instead of rollback. So I created a patch to
accept this word as an alias for
On Fri, Apr 23, 2010 at 10:58:40AM -0500, Terry Brown wrote:
I asked on IRC if there was any way to make \d behave like \d+ by default,
and davidfetter said no but suggest it here.
endpoint_david pointed out you could use \d- to get the old behavior if you
wanted to temporarily negate the
On Tue, Apr 27, 2010 at 08:18:13PM -0400, Robert Haas wrote:
On Tue, Apr 27, 2010 at 6:45 PM, Kjell Rune Skaaraas kjell...@yahoo.no
wrote:
[snip]
I saw some indications that this might be a minority opinion, well I would
like to cast a vote FOR this functionality. The workarounds are ugly,
On Mon, May 10, 2010 at 01:35:32PM -0700, Josh Berkus wrote:
deleted,
or on a reporting read-only clone of your database which gets
recreated very
night and is not used for failover. High quality hardware alone
s/very/every/
or
s/very night/periodically/
Ross
--
Ross
On Tue, Jun 15, 2010 at 01:25:33PM -0700, David E. Wheeler wrote:
On Jun 15, 2010, at 1:12 PM, Bruce Momjian wrote:
This was just posted to announce. Seems the community now has to
compete with another extension-based infrastructure if we ever get
around to developing one of our own.
On Tue, Jun 15, 2010 at 03:42:59PM -0700, David E. Wheeler wrote:
On Jun 15, 2010, at 3:22 PM, Bruce Momjian wrote:
I totaly agreed you need funding, and you are very well qualified to do
this, and it is a badly needed facility.
Thanks.
The problem I had is that the effort appeared
On Sat, Jun 26, 2010 at 01:19:57PM -0400, Robert Haas wrote:
I'm not sure. What does seem clear is that it's fundamentally at odds
with the admission control approach Kevin is advocating. When you
start to run short on a resource (perhaps memory), you have to decide
between (a) waiting for
On Thu, Jul 15, 2010 at 04:20:12PM +0100, Simon Riggs wrote:
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
On Tue, Jan 11, 2011 at 11:06:18AM -0800, Josh Berkus wrote:
It makes it very convenient to set up standbys, without having to worry
that you'll conflict e.g with a nightly backup. I don't imagine people
will use streaming base backups for very large databases anyway.
Also, imagine that
On Thu, Feb 03, 2011 at 10:21:28AM +0200, Anssi Kääriäinen wrote:
On 02/02/2011 08:22 PM, Dimitri Fontaine wrote:
Either one line in the Makefile or a new file with the \i equivalent
lines, that would maybe look like:
SELECT pg_execute_sql_file('upgrade.v14.sql');
SELECT
On Thu, Feb 03, 2011 at 04:31:08PM +0100, Dimitri Fontaine wrote:
Ross J. Reedstrom reeds...@rice.edu writes:
Hmm, how about allowing a list of files to execute? That allows the
Sure. I still don't see why doing it in the control file is better than
in the Makefile, even if it's already
On Mon, May 23, 2011 at 11:08:40PM -0400, Robert Haas wrote:
I don't really like the idea of adding a GUC for this, unless we
convince ourselves that nothing else is sensible. I mean, that leads
to conversations like this:
Newbie: My query is slow.
Hacker: Turn on enable_magic_pixie_dust
On Thu, May 19, 2011 at 04:13:12PM -0400, Alvaro Herrera wrote:
Excerpts from Robert Haas's message of jue may 19 15:32:57 -0400 2011:
That's a bit of a self-defeating argument though, since it implies
that the effect of taking an exclusive lock via LockSharedObject()
will not simply
On Wed, May 25, 2011 at 01:29:05PM -0400, Robert Haas wrote:
On Wed, May 25, 2011 at 1:06 PM, Greg Smith g...@2ndquadrant.com wrote:
On 05/24/2011 04:34 PM, Robert Haas wrote:
I've been looking into a similar refactoring of the names here, where we
bundle all of these speed over safety
On Tue, May 31, 2011 at 04:19:29PM +0200, Florian Pflug wrote:
Sorry for the self-reply but I figured it'd be helpful to add information
that I discovered only after my initial post.
On May30, 2011, at 15:17 , Florian Pflug wrote:
The XPath expression 'name(/*)', for example, is supposed to
On Tue, May 31, 2011 at 11:35:01AM -0500, Kevin Grittner wrote:
Alvaro Herrera alvhe...@alvh.no-ip.org wrote:
This patch allows you to initially declare a CHECK constraint as
NOT VALID, similar to what we already allow for foreign keys.
That is, you create the constraint without
On Wed, Jun 01, 2011 at 04:58:36PM -0400, Robert Haas wrote:
On Wed, Jun 1, 2011 at 4:47 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Robert Haas robertmh...@gmail.com writes:
I guess the real issue here is that m1.id m2.id has to be evaluated
as a filter condition rather than a join qual.
On Thu, Jun 02, 2011 at 01:43:16PM -0400, Tom Lane wrote:
=?utf-8?q?Rados=C5=82aw_Smogura?= rsmog...@softperience.eu writes:
Tom Lane t...@sss.pgh.pa.us Thursday 02 of June 2011 16:42:42
Yes. I think the appropriate problem statement is provide streaming
access to large field values, as an
On Fri, Jun 03, 2011 at 11:22:34AM -0400, Robert Haas wrote:
On Fri, Jun 3, 2011 at 1:14 AM, Noah Misch n...@leadboat.com wrote:
No, there's no need to do that. The domain is an array, not merely
something
that can be coerced to an array. Therefore, it can be chosen as the
polymorphic
On Mon, Jun 06, 2011 at 12:53:49PM -0400, Robert Haas wrote:
I don't have clear feeling on this question in general, but if we're
going to break this up into pieces, it's important that they be
logical pieces. Putting half the feature in core and half into an
extension just because we can
On Wed, Jun 15, 2011 at 09:14:16PM -0400, Stephen Frost wrote:
Bruce,
* Bruce Momjian (br...@momjian.us) wrote:
I have researched this and need feedback.
In general, I like the whole idea of using random/special ports for the
duration of the upgrade. I agree that we need to keep the
On Thu, Jun 16, 2011 at 09:48:12AM -0400, Bruce Momjian wrote:
Tom Lane wrote:
Ross J. Reedstrom reeds...@rice.edu 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
Right, but I think he needs the it's not easy, here's the whole
workflow overview first.
Ross
--
Ross Reedstrom, Ph.D. reeds...@rice.edu
Systems Engineer Admin, Research Scientistphone: 713-348-6166
Connexions http://cnx.org
On Fri, Jun 17, 2011 at 10:20:04AM -0400, Alvaro Herrera wrote:
Excerpts from Florian Pflug's message of vie jun 17 10:03:56 -0400 2011:
How is that worse than the situation with =~ and ~=?
With =~ it is to the right, with ~= it is to the left.
To throw my user opinion into this ring (as
On Fri, Jun 17, 2011 at 05:21:10PM +0200, Florian Pflug wrote:
On Jun17, 2011, at 17:15 , Ross J. Reedstrom wrote:
On Fri, Jun 17, 2011 at 10:20:04AM -0400, Alvaro Herrera wrote:
Excerpts from Florian Pflug's message of vie jun 17 10:03:56 -0400 2011:
How is that worse than the situation
On Tue, Jun 21, 2011 at 10:15:50AM -0400, Alvaro Herrera wrote:
Excerpts from Pavel Stehule's message of mar jun 21 10:04:26 -0400 2011:
2011/6/21 Alvaro Herrera alvhe...@commandprompt.com:
Excerpts from Pavel Stehule's message of mar jun 21 00:59:44 -0400 2011:
yes - it has a sense.
On Fri, Aug 12, 2011 at 10:14:58PM +0300, Marko Kreen wrote:
On Thu, Aug 11, 2011 at 5:46 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Marko Kreen mark...@gmail.com writes:
On Wed, Aug 10, 2011 at 9:19 PM, Tom Lane t...@sss.pgh.pa.us wrote:
... which this approach would create, because digest()
On Tue, Nov 16, 2010 at 09:41:37PM -0500, Robert Haas wrote:
On Tue, Nov 16, 2010 at 8:15 PM, KaiGai Kohei kai...@ak.jp.nec.com wrote:
If we don't need a PoC module for each new hooks, I'm not strongly
motivated to push it into contrib tree.
How about your opinion?
I'd say let it go,
On Fri, Nov 19, 2010 at 04:57:03PM +0900, KaiGai Kohei wrote:
(2010/11/18 2:17), Robert Haas wrote:
If KaiGai updates the code per previous discussion, would you be
willing to take a crack at adding documentation?
P.S. Your email client seems to be setting the Reply-To address to a
On Fri, Dec 03, 2010 at 05:16:04PM -0500, Robert Treat wrote:
On Fri, Dec 3, 2010 at 4:41 PM, Josh Berkus j...@agliodbs.com wrote:
However, I don't see why we need (column_list). Surely the index has a
column list already?
ALTER TABLE table_name ADD CONSTRAINT pk_name PRIMARY KEY USING
On Fri, Sep 02, 2011 at 02:05:45PM -0500, k...@rice.edu wrote:
On Fri, Sep 02, 2011 at 09:54:07PM +0300, Peter Eisentraut wrote:
On ons, 2011-08-31 at 13:12 -0500, Ross J. Reedstrom wrote:
Hmm, this thread seems to have petered out without a conclusion. Just
wanted to comment
On Mon, Oct 31, 2011 at 09:14:48AM -0400, Andrew Dunstan wrote:
The fact is that if you have 100 columns and want 95 of them, it's
very tedious to have to specify them all, especially for ad hoc
queries where the house SQL standards really don't matter that much.
It's made more tedious by the
On Tue, Nov 01, 2011 at 10:13:52AM -0400, Andrew Dunstan wrote:
On 11/01/2011 09:52 AM, Tom Lane wrote:
Simon Riggssi...@2ndquadrant.com writes:
Why not leave it exactly as it is, and add a previous_query column?
That gives you exactly what you need without breaking anything.
That would
On Mon, Mar 07, 2011 at 03:45:17PM -0300, Alvaro Herrera wrote:
Excerpts from Tom Lane's message of lun mar 07 15:16:31 -0300 2011:
If we do that then it becomes worth wondering what the -docs list is for
at all. Maybe we *should* get rid of it; I dunno. I see your point
about how the
On Fri, Mar 11, 2011 at 09:03:33AM -0500, Robert Haas wrote:
On Fri, Mar 11, 2011 at 8:21 AM, Fujii Masao masao.fu...@gmail.com wrote:
In that case, the last write WAL timestamp would become equal to the
last replay WAL timestamp. So we can see that there is no lag.
Oh, I see (I think).
On Fri, Mar 18, 2011 at 11:00:19PM -0400, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Fri, Mar 18, 2011 at 10:19 PM, Andrew Dunstan and...@dunslane.net
wrote:
On 03/18/2011 09:18 PM, Robert Haas wrote:
all balls seems like a colloquialism best avoided in our
On Thu, Apr 21, 2011 at 11:16:45AM -0400, Tom Lane wrote:
Robert Haas robertmh...@gmail.com writes:
On Thu, Apr 21, 2011 at 2:43 AM, Peter Eisentraut pete...@gmx.net wrote:
I think to really address that problem, you need to think about shorter
release cycles overall, like every 6 months.
On Mon, May 09, 2011 at 03:57:12PM -0400, Robert Haas wrote:
On Mon, May 9, 2011 at 2:58 PM, Bruce Momjian br...@momjian.us wrote:
Tom this collation stuff has seen more post-feature-commit cleanups than
I think any patch I remember. Is there anything we can learn from this?
How about
On Tue, May 10, 2011 at 07:21:16PM +0200, Andres Freund wrote:
On Tuesday, May 10, 2011 07:08:23 PM Ross J. Reedstrom wrote:
On Mon, May 09, 2011 at 03:57:12PM -0400, Robert Haas wrote:
On Mon, May 9, 2011 at 2:58 PM, Bruce Momjian br...@momjian.us wrote:
Tom this collation stuff has
101 - 178 of 178 matches
Mail list logo
