inherently insecure. If that is more
than just a philosphical opinion, I wonder if there should be additional
hurdles in place to enable this on that platform. Note that isn't an
objection from me, though I'm curious if any of the Sun guys want to chime in
on this.
--
Robert Trea
...
>
What's the use case for extending SELECT on table to SELECT on sequence ?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
The current wording implies that you replace arg1 with arg2 in arg3, but
replace actually replaces occurences of arg2 with arg3 in arg1. Attached
patch makes the function comment more closely resemble that, and is more
in-line with the docs wording as well.
--
Robert Treat
Build A Brighter
o require a lot of custom monitoring
> infrastructure that is not present in this patch, and furthermore that
> this patch doesn't especially aid the development of.
>
This patch makes that a 1 line sql call, which can be plugged into any number
of monitoring systems.
--
Robe
at those settings
5) Determine the number of log files that will need to be replayed in the
event of a crash
6) Helps give an indication on if you should enter a manual checkpoint before
issuing a pg_start_backup call
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware}
On Friday 04 April 2008 00:09, Greg Smith wrote:
> On Thu, 3 Apr 2008, Robert Treat wrote:
> > You can plug a single item graphed over time into things like rrdtool to
> > get good trending information. And it's often easier to do this using
> > sql interfaces to get th
> 3. As of PG 8.3, the bgwriter tries very hard to make the elapsed time
> > of a checkpoint be just about checkpoint_timeout *
> > checkpoint_completion_target, regardless of load factors. So unless
> > your settings are completely broken, measuring the actual time isn't
ng everything into the log files isn't always sufficient (says the guy
who maintains a remote admin tool)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-patches mailing list (pgsql-patches@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-patches
ase), it also holds an exclusive lock on its permanent
transaction ID until it ends."
ISTM that by removing the transaction column, there is no way to see the XID
for relations thats have been updated (which by definition will have locks on
them). Am I mis-reading the docs, or have we lost t
On Sunday 01 July 2007 17:59, Joe Conway wrote:
> Joe Conway wrote:
> > Robert Treat wrote:
> >>>> Joe Conway <[EMAIL PROTECTED]> writes:
> >>>
> >>> Well certainly dbi-link has the exact same issue.
> >>
> >> dbi-link o
date would install the security fix into
> > existing installations, without need for any DBA intervention.
> >
> > * It does not take away functionality that has perfectly legitimate uses.
>
> Agreed.
>
I think this will break backwards compatability though. ie. non-superuser
On Sunday 01 July 2007 13:15, Gregory Stark wrote:
> "Joe Conway" <[EMAIL PROTECTED]> writes:
> > Robert Treat wrote:
> >> Patch based on recent -hackers discussions, it removes usage from
> >> public, and adds a note to the documentation about why this i
Patch based on recent -hackers discussions, it removes usage from public, and
adds a note to the documentation about why this is neccessary.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Index: contrib/dblink/dblink.sql.in
s.com/";>http://www.benchmarkresources.com
>.. -
> 1.12) What is configure all about?
>
> The files configure and configure.in are part of
> --- 512,517
>
>
> -------(end of broadcast)---
> TIP 2: Don'
would have made a real difference.
>
If we were going to implement this (and I'm a tad skeptical as well), wouldn't
it be better if the warning occured at the end of vacuum, and told you how
much memory was actually needed, so you'd know what maintainence_work_m
Subject pretty much says it all. Somewhere the answer to 1.19 got
regurgitated to 2.9, so this corrects that and adds an answer to the
SCMS question based on recent hackers thread.
--
Robert Treat
Database Architect
OmniTI Computer Consulting, Inc. -- http://www.omniti.com/
Index
ease)
> >
> > Changes
> >
> > - added -r option to specify maxretries
> > - -l option for Windows Vista (only) using mklink
> > - Windows examples and docs added to readme
> > - code restructured to allow more easy customization
> > - bug fix
On Wednesday 07 February 2007 23:35, Bruce Momjian wrote:
> Robert Treat wrote:
> > Can someone apply Jim's patch at least to HEAD and REL8_2_STABLE? We
> > recently got a report of a broken link on the website due to this; seems
> > it is still broken...
>
> OK
ions outside
of a new release?
Even if the answer is 'no', it'd still be good to make the change in
CVS. See attached (btw, this is in the docs back to at least 7.2).
--
Jim Nasby[EMAIL PROTECTED]
EnterpriseDB http://enterprisedb.com
n tests and all my tests as well...
>
> i think the patch is ready to be applied to HEAD, any committer want
> to review it?
Why is this PGC_SUSET? ISTM it should be PGC_USERSET.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end
when doing INSERT INTO foo SELECT *, it could be
a nice improvement as well. Am I overlooking something?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
pages.
>
> I wasn't aware those used the optimization. Seems they all should be
> documented somewhere.
Might I suggest somewhere under chapter 27, with something akin to what we
have for documenting lock levels and the different operations that use them.
We document the reasons you wan
ose.
The current terminology of live and dead is already used in many places in the
documentation and in userspace; mostly around the need for maintainance of
dead tuples within tables, reindex cleaning up dead pages, and even in the
vacuum commands output (n dead tuples ca
I noticed that the section on pl langs points to appendix H to find out about
additional pl's, but there is no info there to speak of. The attached patch
ads a list of external pl's and cleans up some other links and wording in
those areas
--
Robert Treat
Build A Brighter LAMP :: Li
just fixes up a couple of minor points,
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
Index: README.tsearch2
===
RCS file: /projects/cvsroot/pgsql/contrib/tsearch2/README.tsearch2,v
retrieving
the other way, it seems
the guy who actually codes something offers a better solution than
handwaving... people have also had plenty of time to come up with a
replacement if that's what they really wanted.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
-
php/etc...). This solution would solve that problem for us, so I would
lean toward including it. I would be interested in hearing from actual users
who really need the subselect version though, but right now my thinking is
that group is a small minority of who would benefi
th CVS, but do you know if it can
support those types of configurations?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
s
seems indicated, at least.
>
> Oh, no doubt. I tried to fix as much as I find, including a bunch of
> stuff already there. However, I do not claim, in any way to be an editor.
>
The following patches provide some editorializing for Joshua's patches.
--
Robert Treat
Build A B
itself.
There were a couple of other minor things I noticed too... Joshua, do you mind
if I make some changes and resubmit this patch?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
Updates link to support companies from old techdocs to main website
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: doc/src/FAQ/FAQ.html
===
RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html
Updates the link for the sql 2003 spec, also fixes a spelling error.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: FAQ_DEV.html
===
RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ_DEV.html,v
lined
> > to do no more on the gounds of insufficient demand. Let's decide before
> > too much bitrot occurs, though.
>
> +1 :)
>
+1
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
Attached patch fixes a couple of spelling mistakes in the FAQ
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: FAQ.html
===
RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html,v
retrieving
e .so is there.
>
While I agree with the above (having that for tsearch2 would be nice too) I
think we ought to keep in mind the idea of sql based modules. Nothing jumps
to mind here ppa wise, but I could see an application looking to see if
mysqlcompat was installed before running if it had a goo
o the modules
> in general...
>
> Personally I think it's a good idea, except: where is this info going
> to be displayed or used?
>
Marko's suggestion on producing a list of installed modules comes to mind, and
I suspect tools like pgadmin or ppa will want to be a
Attached patch updates FAQ 2.3 updating the link for the GUI Tools page to the
new page in the new techdocs, along with some verbage changes. Note this
link should be updated by all translators.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: FAQ.html
at http://sqlcourse.com.
>
> first link is broken, second moved
>
thanks for the report, the attached patch updates that section.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: FAQ.html
===
On Thursday 16 February 2006 00:27, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > As stated, the following patch adds a list of patch submission guidelines
> > based on Simon Riggs suggestions to the developers FAQ.
>
> A couple minor comments ...
>
On Thursday 16 February 2006 00:27, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > ! The patch should be generated in contextual diff format and
> > should !be applicable from the root directory. If you are
> > unfamiliar
> &
On Tuesday 14 February 2006 20:42, Robert Treat wrote:
> On Tuesday 14 February 2006 16:00, Martijn van Oosterhout wrote:
> > > I would like to suggest that we increase substantially the FAQ entries
> > > relating to patch submission. By we, I actually mean please could the
that I set the connection limits
lower on most of the installations I do (given than most installations are
not production webservers). There is also the argument to be made that just
because systems these days have more memory doesn't mean we have to use it.
--
Robert Treat
Build A Bri
afaict) and looking in
pg_settings there would be no indication that anything was wrong, other than
autovacuum being set to off (perhaps if it was set to 'error, stats disabled'
or some such it might be better?)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} Postgr
r
> versions, and two months after feature freeze isn't the time to start
> making that happen.
>
That said, number of folks have looked at this problem and agree it would be
nice to do, they just haven't formed a consensus on how to do it. If you
have a plan for how you would want
uot;
>
good catch. I looked around for any other instances of this and didnt find
any... attached is a patch to correct this one.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: information_schema.sgml
===
www.postgresql.org/docs/8.0/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
On Monday 04 July 2005 13:25, Bruce Momjian wrote:
> Robert Treat wrote:
> > Actually I'd agree with Tom, pg_dbfile_size is ugly, and suggest to me I
> > could use a filename as an argument. ISTM that if we think that
> > functions like pg_database_size and pg_tabl
that feel we need both. I'm not sold we need a function
that can return either an index or table size, but if so something like
pg_object_size seems ambigious enough to work, and is future proof enough to
handle things like materialized views when and if they arise.
Just my .02 :-)
--
Robert T
on a question from newbies... "does postgresql have a default
database to get started with?" They'll see this database and begin creating
schema and using this as thier main database, and I think we ought to avoid
that. If people don't like pg_system, pg_addons seem like a much s
gex_replace which only
replaces the first occurance? There's something to be said for consitancy
within pgsql itself.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Found this in my cvs tree, guess I should submit it. Should give the proper
tagging for the compatability section of the alter domain page
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: alter_domain.sgml
On Saturday 28 May 2005 11:12, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > I'm not against the idea of a config variable, but this is what, the
> > third or fourth go around on this? It seems rather unfair to put this
> > burden upon the curre
burden upon the
current patch writer at this stage of the game if someone wants to code
the config option let them, put it shouldn't be a barrier to having the
current patch be applied.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---
On Friday 27 May 2005 15:09, Peter Eisentraut wrote:
> Robert Treat wrote:
> > > I see hardly any use case for showing only user-defined functions
> > > or types by default. I think consistency is not necessarily
> > > desirable here.
> >
> > See the a
mind? I'm having trouble coming up with
a way to do it cleanly.
>
> I see hardly any use case for showing only user-defined functions or
> types by default. I think consistency is not necessarily desirable
> here.
>
See the archives for previous discussion and
A couple of the domain commands were missing "see also" references, this patch
adds those references.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: alter_domain.sgml
===
RCS file:
On Sunday 01 May 2005 11:58, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > The example given in create domain seems to be broken. ISTM it requires
> > some extra escaping to be usable (at least in my goings on today it sure
> > was, and I the entries in
On Saturday 30 April 2005 21:14, Alvaro Herrera wrote:
> On Sat, Apr 30, 2005 at 06:12:27PM -0400, Robert Treat wrote:
> > --- 167,174
> >
> > CREATE DOMAIN us_postal_code AS TEXT
> > CHECK(
> > !VALUE ~ '^\\d{5}$'
> > ! OR VA
.
Oh.. and Andrew @ Supernews had nothing to do with this ;-)
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: create_domain.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/ref
27;t see a good reason to treat this setting different
from all others and explicitly forbid this use from people, especially
when I can imagine people coming from other dbs where this behavior is
more common who might in fact expect it to work this way.
Robert Treat
--
Build A Brighter Lamp :: Linu
This patch updates a number of urls in a number of files. Most are just
poinitng to the TODO list within the main website.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
? url_update.patch
Index: doc/src/FAQ/FAQ.html
Inspired by comments from steve <[EMAIL PROTECTED]>, adds a few urls for
more download options.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: installation.sgml
===
RCS file: /projects/c
sql_savepoint instead, that way it
> follows our 'don't begin things with pg_' philosophy.
>
I was actually thinking of calling it something like
pg_ thinking that would be pretty unique within a
transaction, though having a specific documented name seemed ok too.
Robert Trea
ansaction blocks
ERROR: RELEASE SAVEPOINT may only be used in transaction blocks
I've attached a revised patch which fixes the problem, however I'm sure there
is a better way. Thanks to Neil for putting up with me on irc :-)
--
I guess this has to be saved for 8.1... shame.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: createuser.c
===
RCS file: /projects/cvsroot/pgsql/src/bin/scripts/createuser.c,v
retrieving
Changes the doc's to reflect what the user will find as default.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: runtime.sgml
===
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/runtime.s
This is certainly nicer than what I had. This seems to be mostly a copy/paste
change, but if I need to submit a new patch lmk.
Robert Treat
On Saturday 13 November 2004 03:57, Gavin Sherry wrote:
> Robert,
>
> I think there are some mistakes with your addition. Here's a rework
People seem to get confused about just what the TODO list is, this patch gives
a more verbose explanation of how it works.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: TODO
===
RCS file
added question on website development
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: FAQ.html
===
RCS file: /projects/cvsroot/pgsql/doc/src/FAQ/FAQ.html,v
retrieving revision 1.227
diff -c
This patch makes mention to use the newer pg_dump when migrating, as suggested
by a few folks.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: backup.sgml
===
RCS file: /projects/cvsroot/pgsql
abase from a limited subnet, but with trust
authentication since random people inside the company will sometimes
want to take a look at what I am cooking up. For my needs I use the
superuser account who can access all databases but must come through
ident on a unix socket. Different strokes for dif
he aggregate functions page gets picked up in the index entry for
any/some I think that would be appropriate.
Thanks for your efforts.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
for subqueries
and arrays, I'd like to give people looking for the sql spec aggregate
functions at least a chance of finding these.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9:
resubmitting FAQ updates based on html version.
Robert Treat
On Friday 19 March 2004 10:56, Bruce Momjian wrote:
> Can I get HTML diffs against contrib/src/FAQ.html?
>
> ---
>
> Robert Treat wrote:
> &
I think I can work that up. Out of curiosity are the plain text files
generated from the html files? Also I noticed that not all plain text
FAQ's have html FAQ's associated with them... is that by design or just
the fact that no one has bothered to bring them up to speed?
Robert Tre
version of
that statement.
Robert Treat
On Tuesday 25 November 2003 20:30, Christopher Kings-Lynne wrote:
> Ummm - surely the original was correct?
>
> Chris
>
> Robert Treat wrote:
> > Marcos Truchado <[EMAIL PROTECTED]> reported this on -docs
> >
On Tue, 2003-11-25 at 14:24, Peter Eisentraut wrote:
> Tom Lane writes:
>
> > Robert Treat <[EMAIL PROTECTED]> writes:
> > > ! SELECT INTO users_rec * FROM users WHERE user_id=3;
> > > --- 986,993
> > > ! SELECT * FROM users WHERE user_id
Sorry Neil. I thought I recalled you submitting a similar patch, but
must have missed it in the archives and didn't see the change reflected
in cvs so assmeme'd that your change was in a different place.. :-(
Robert Treat
On Tue, 2003-11-25 at 14:04, Neil Conway wrote:
> Robert
On Tue, 2003-11-25 at 11:24, Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > ! SELECT INTO users_rec * FROM users WHERE user_id=3;
> > --- 986,993
> > ! SELECT * FROM users WHERE user_id=3 INTO users_rec;
>
> Why do you want to change
Marcos Truchado <[EMAIL PROTECTED]> reported this on -docs yesterday.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQLIndex: plpgsql.sgml
===
RCS file: /projects/cvsroot/pgsql-server/doc/sr
better late than never?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: INSTALL
===
RCS file: /projects/cvsroot/pgsql-server/INSTALL,v
retrieving revision 1.91
diff -c -r1.91 INSTALL
*** INSTALL
Change some awkward wording in the pg_autovacuum README file. I really
only read this because of Niel :-)
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: README.pg_autovacuum
===
RCS file
seemed like a typo in one of the appendix tables
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: datetime.sgml
===
RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/datetime.sgml,v
retrieving
On Friday 05 September 2003 16:24, Peter Eisentraut wrote:
> Robert Treat writes:
> > I didn't see it documented anywhere that a 0 in attypid of pg_attribute,
> > and given the note on the need to match pg_type lest failure seems to
> > warrant the mention.
>
> A
I didn't see it documented anywhere that a 0 in attypid of pg_attribute,
and given the note on the need to match pg_type lest failure seems to
warrant the mention.
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
Index: src/include/catalog/pg_attrib
85 matches
Mail list logo
