The following documentation comment has been logged on the website:
Page:
https://www.postgresql.org/docs/9.4/static/runtime-config-file-locations.html
Description:
In various places (e.g. stackoverflow), I've seen people suggest having
pg_xlog ion a different disk (i.e. not in /var/lib/pgsql/9.
a way to accomplish this? Would people be against the idea?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
On Mon, 2003-06-30 at 17:40, Peter Eisentraut wrote:
> Robert Treat writes:
>
> > I'd like to add column "headers" to the *bottom* of the sql keywords
> > table, but I can't simply add a duplicate at the bottom. Is
> > there a way to accomplish thi
We plan to have major releases every four months.
>
should this last part be changed? we don't plan to have major releases
every four months...
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)
t the door.
Robert Treat
On Tue, 2003-11-18 at 17:17, Bruce Momjian wrote:
> Oliver Elphick wrote:
> > On Tue, 2003-11-18 at 02:54, Christopher Browne wrote:
> > ...
> > > > cd doc/src/sgml
> > > > make postgres.pdf
> > > >
> > > > but ope
n the eyes? What I find particularly difficult are the
> function parameter columns; the mix of "normal" italics with "bold" italics.
>
> Comments? Responses?
>
Whatever we had in 7.3 we should switch back to:
http://www.postgresql.org/docs/7.3/static/fu
uch of that section was rewritten into this:
http://www.postgresql.org/docs/current/static/multibyte.html
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 8: explain analyze is your friend
On Monday 12 January 2004 01:34, Karel Zak wrote:
> On Sun, Jan 11, 2004 at 11:43:07PM -0500, Robert Treat wrote:
> > On Thursday 08 January 2004 07:36, Karel Zak wrote:
> > > Hi,
> > >
> > > docs for 7.3 contains information how se
ly better than someone personal
home page.
Chris, is there some way to accomplish this with gborg?
Josh, is this something that Gforge would give us?
Anyone know what the guys working on the perl interface have done?
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreS
I'd rather point to a pdf or html doc. If you don't
mind us hosting ourselves, I'll put it up as the unzipped pdf. LMK
Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
)
IMHO we ought to try to keep the _tutorial_ free of things that are generally
considered against relational design. If we must keep them, move them into
thier own section and lable them accordingly.
Robert Treat
---
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
-
install there at one time. I resolved to
> take notes this time. I'm offering you the results so you can put it in
> the FAQ under the heading: "I just installed my RPMs on FC2. Now what?"
>
ISTM this should go up onto techdocs rather than in the regular documentation?
If
ly been getting drilled to regenerate the idocs on the
website with each new release in the 7.4.x series.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
d then create a new
faq faq_win32_native based the pginstaller one. Does anyone feel they ought
to be combined? I guess another alternative is jut remove faq_mswin from the
main sources and then leave it up to cygwin/native projects to maintain thier
own faqs, with perhaps a single questi
with
specific links to both a cygwin and native specific faqs, but barring that,
we could combine both documents together and make a 3 sectioned windows
specific faq, with a section on general stuff, cygwiun stuff, and native
stuff. Both projects could then just link to t
ed the whole section into one big
> alphabetical list, and while that has obvious drawbacks, I feel that
> it's already much more usable than what we have now.
>
> Other ideas?
I thought runtime-config was supposed to be ordered in the same order as the
default postgresql.conf ?
--
the faq -> http://www.postgresql.org/docs/faqs/FAQ.html#4.8
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 7: don't forget to increase your free space map settings
subdir value in the Makefile
> you can place it in a different directory in a PostgreSQL tree)."
>
> Surely this should refer to 8.0 also?
Depends on if it actually works in 8.0 I'd imagine.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
-
nothing
> special about that location... feel free to move it around :-)
>
> Mark
I thought it was more correct to use < rather than < inside of
tags?
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(e
someone suggested that the insert command at the end of
http://wwwmaster.postgresql.org/docs/8.0/interactive/dml.html would be
better if it were a link like the copy command is. Is there some reason not
to make it a link? I notice most commands are not done this way.
--
Robert Treat
Build
t about PostgreSQL. The
entry below FAQ on the left hand leads to a link collection, the first
of which points to a chinese translation of the FAQ at
http://www.pgsqldb.org/postgres-faq.html.
Regards,
Robert
---(end of broadcast)---
TIP 5: Have
nce obviously rules can be on more than just tables.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Don't 'kill -9' the postmaster
to * and ? in search boxes, even if they are DBAs), but the problem is
> it doesn't seem to allow escaping them. For example, search on
> 'pg_stat_activity current_query'.
Try searching "pg_stat_activity" "current_query" instead.
--
Robert Treat
osted somewhere more reliably.
>
Well, I'm happy to host it on techdocs if he wants to move it there.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the pl
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
===
f the
web stuff is actually worked on, so the folks who know the system all hang
out there.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
On Thursday 13 October 2005 16:10, Peter Eisentraut wrote:
> Alvaro Herrera wrote:
> > At the bottom of the TOC we have very long lists of tables, figures
> > and examples. I recall somebody said we could get rid of them?
>
> They're gone now.
Doh.
--
Robert T
Nice little article on docbook xml
http://www.redhat.com/magazine/016feb06/features/docbook_xml/
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will
uld happen on Windows. Um, help?
>
Could we require contrib authors to provide their documentation as sgml, and
then have the doc build process loop in each contrib module as an appendix
inside the official docs?
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
On Saturday 18 March 2006 02:00, Tom Lane wrote:
> "Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> > On Fri, Mar 17, 2006 at 04:19:58PM -0500, Robert Treat wrote:
> >> Could we require contrib authors to provide their documentation as sgml,
> >> and t
similarly here.
http://archives.postgresql.org/pgsql-general/2006-03/msg00891.php
Feel free to submit an additional doc comment.
--
Robert Treat
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
On Wednesday 22 March 2006 15:14, Tom Lane wrote:
> However, the arguments Robert pointed to had to do with concurrent
> access to the table, and somehow I am not seeing the use-case for ALTER
> COLUMN TYPE on a table that's being actively used by other clients.
> It seems unlike
icable. That really is a
factor, most of the comments would need to be reworded to be added into the
docs proper.
In the past these ideas were rejected as either off-topic or that it would
turn this list into a high traffic list... if peoples opinions have changed,
it could be arranged.
--
On Thursday 23 March 2006 17:46, David Fetter wrote:
> On Thu, Mar 23, 2006 at 04:46:02PM -0500, Robert Treat wrote:
> > > ...and it's unlikely that they will, now or later, without
> > > somebody whose whole job is to monitor those comments and make
> > > pat
).
In the mean time, the attached patch updates the link.
--
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
retr
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)---
TIP 6:
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
ocs/techdocs.54
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
that
allows any community member to put online guides and documentation into
place, made specifically for the purpose of things like what your looking
for.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)-
certain how best the postgresql specific probes will be used, but I
might disagree with the above take as we're already using some kernel level
dtrace probes to make DBA oriented tools... see
http://www.lethargy.org/~jesus/archives/74-PostgreSQL-performance-through-the-eyes-of-D
the front page. The text is more or less copied
> directly from the FAQ. Updates to the text are always welcome ;-)
>
> I suggest that we remove it from the FAQ, or replace it with a reference
> to the website, once the site has updated.
>
I'd suggest we add this into the
es=# select min (age(relfrozenxid)) from pg_class where relkind = 'r';
min
----
253045
(1 row)
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 3: Have you checked our exten
ow_level to effect whether the last ANALYZE / VACUUM is recorded.
> (Plus, the optimization is not even enabled with the default
> postgresql.conf settings.)
>
+1
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
or something.
>
> Any ideas how we can best fix this?
>
Honestly found the response that actually brings glee to peoples face is
pointing them toward Andrea's feature matrix. Perhaps we ought to think
about making that more official ?
--
Robert Treat
Build A Brighter LAMP :
link for libpqxx should either be reverted or changed to libpqxx.org, of
the three, .tk is the least desired.
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 4: Have you search
question a bit on irc and
there aren't any more appropriate answers for any released version than what
the FAQ contained...
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
---(end of broadcast)---
TIP 6: explain analyze is your friend
changed to seconds. I thought someone told me <5 minutes a
> while ago but I might have been mistaken.
I might question the strict reference to Slony here. AIUI you could do the
same thing with Bucardo and a couple of other replication solutions as well.
--
Robert Treat
Build A Brighter LA
On Tuesday 16 October 2007 15:46, Bruce Momjian wrote:
> Robert Treat wrote:
> > On Friday 12 October 2007 14:04, Ian Barwick wrote:
> > > Hi
> > >
> > > attached some minor corrections, mainly completion of removal of
> > > the "relation
ou
have and that you cannot give away. In the U.S., you can give copy rights
away, however you can only do so to a defined legal entity, of which the PGDG
is not one. This can change somewhat depending on country and depending upon
employer agreements, but since no one is employed by the PGDG, it
the person to contact if you had questions/comments/patches/etc...
about a specific contrib module. I wonder if people would still get the same
level of help if those names are removed and they have to go to the regular
mailing lists for help (which contrib authors may not follow).
--
Robe
sing configure.
> A post installation step is fine but I think it needs to be documented
> as such.
>
There are instructions on how to install them at
http://www.postgresql.org/docs/8.3/interactive/contrib.html, but your right
they don't seem to be mentioned anywhere in the install s
he release process, but it was pretty much DOA as well.
Probably too late to do anything about this now, though I wonder, do we plan
to put 8.3.2 tarballs into the ftp-archives? We have 8.2.2 tarballs
available, though I can't imagine why anyone would need them.
--
Robert Treat
Build A
ke it could use some rewording...
thoughts?
--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Fri, Apr 2, 2010 at 2:06 AM, Fujii Masao wrote:
> On Fri, Apr 2, 2010 at 2:58 AM, Robert Haas wrote:
>> It's probably also easy to fix so that it doesn't NEED to be documented.
>>
>> The thing is, when dealing with new features, we reduce our overall
>>
On Tue, Apr 20, 2010 at 5:47 AM, Fujii Masao wrote:
> On Tue, Apr 20, 2010 at 11:04 AM, Robert Haas wrote:
>> Instead of doing this, could we just change the logic in InitPostgres?
>>
>> Current logic says we hit the connection limit if:
>>
On Tue, Apr 20, 2010 at 9:40 AM, Tom Lane wrote:
> Robert Haas writes:
>> If replication connections can use up superuser_reserved_connections
>> slots, then it's very possible that this safety valve will fail
>> completely.
>
> Only if
_reserved_connections might find that no reserved connections
remained for interactive access to the database.)
> Since 3. is confusing for me, I like 1. or 2.
What do others think?
...Robert
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Tue, Apr 20, 2010 at 7:53 PM, Tom Lane wrote:
> Robert Haas writes:
>> Current logic says we hit the connection limit if:
>
>> if (!am_superuser &&
>> ReservedBackends > 0 &&
>> !HaveNFreeProcs(Reserv
On Wed, Apr 21, 2010 at 12:20 PM, Tom Lane wrote:
> Robert Haas writes:
>> Thanks for the heads up. It doesn't look hard to put a similar test
>> in the walsender code path, but is there any reason to duplicate the
>> code? Seems like we might be able to ju
On Fri, Apr 23, 2010 at 5:54 PM, Erik Rijkers wrote:
> s/the the/the/g; # 2 x
Fixed along with a bunch of others I found.
Thanks,
...Robert
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Tue, May 11, 2010 at 4:41 PM, Josh Berkus wrote:
> The above assumes that there isn't already a project
> 101,
I must be missing something, because I don't see the reference to 101.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
mand.c but I have dropped that from this
patch.(I plan to return to it separately).
5. Documented new macros (and also the PG_GETARG_xxx_P_COPY macros) in
xfunc.sgml. ref/alter_table.sgml also contains documentation for ALTER
COLUMN SET STORAGE.
John Gray
--
Robert Haas
Enter
proposed formatting
elsewhere in the documentation, but the error message is what it is.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql
"pg_notify" to "NOTIFY"?
I think that's because the "Notes" section of that page is the only
place in the documentation that pg_notify() is mentioned... I agree
it looks a little weird, but it's nice that it jumps to the specific
section of the page
about creating new subsection "pg_notify" under "Notes" and placing
> the description about pg_notify in it? Here is the patch.
Looks good to me. Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
I gather that they are
fairly similar in implementation, though I might be wrong about that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.p
ead to maintenance headaches. But on the other hand,
I see no problem mentioning third-party products that are part of the
PG ecosystem.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Wed, May 26, 2010 at 4:03 PM, alvherre wrote:
> Excerpts from Robert Haas's message of mié may 26 15:56:45 -0400 2010:
>
>> > That is an excellent idea, not only for replication, but there are
>> > probably other wiki pages that we should link to from our main docs
On Wed, May 26, 2010 at 5:45 PM, Bruce Momjian wrote:
> Robert Haas wrote:
>> On Tue, May 25, 2010 at 2:15 PM, Bruce Momjian wrote:
>> > Francisco Reyes wrote:
>> >> Bruce Momjian writes:
>> >>
>> >> > Well, I assumed "Londiste"
On Sat, May 29, 2010 at 10:36 PM, Bruce Momjian wrote:
> Josh Berkus wrote:
>> On 5/11/10 3:06 PM, Robert Haas wrote:
>> > On Tue, May 11, 2010 at 4:41 PM, Josh Berkus wrote:
>> >> The above assumes that there isn't already a project
>> >> 101,
&
using
things like ALTER DATABASE ... SET, ALTER USER ... SET, just plain
SET, etc.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
for, though.
http://psqlodbc.projects.postgresql.org/
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
nce? Here is the patch.
I don't think that reads very well. Possibly we could remove
"continuous archive" as a whole, but I don't think we can remove one
word and keep the other.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Compa
On Thu, Jun 10, 2010 at 10:16 AM, Tom Lane wrote:
> Robert Haas writes:
>> On Thu, Jun 10, 2010 at 4:00 AM, Fujii Masao wrote:
>>> The release note says "Allow continuous archive (WAL) files
>>> to be streamed to a standby system" about SR. But no archiv
ur decade-long effort to eliminate the pain of VACUUM,
> VACUUM FULL is not substantially faster by
> rewriting the entire table and
> indexes, rather than moving around single rows to compact space.
>
>
Fixed, thanks for the report.
--
Robert Haas
EnterpriseDB: h
sunderstanding something, but as of 9.0b2 comments
> can still be created for indexes?
You can still comment on the index, but not the columns thereof.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list (pgsql-docs@p
I did some editing of the Hot Standby docs tonight; PFA a proposed patch.
Comments?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
hot-standby-docs.patch
Description: Binary data
--
Sent via pgsql-docs mailing list ([email protected])
To
ussion. Although the original version is pretty complex, it gives the user
> some feel for the particular moment in the past that their snapshot will
> represent. If the original is incorrect, it would be nice to replace it with
> something that doesn't suggest the user might end u
th an optional - or + prefix (not
> unary operators). E.g., ([+\-]?[0-9]+)
You can't assume that a dash followed by digits is always a negative
number. Consider:
SELECT 10-4;
If you we interpret this as "10" followed by "-4", it's a syntax
error. You have to treat
On Wed, Jun 23, 2010 at 2:53 PM, Simon Riggs wrote:
> On Tue, 2010-06-22 at 14:24 -0400, Robert Haas wrote:
>
>> Fixed. See attached.
>
> I started reading this but by chunk seven I only agree with a couple of
> these changes. None of them seem hugely important changes.
>
On Wed, Jun 23, 2010 at 3:05 PM, Robert Haas wrote:
>> We could also allow SELECT ... FOR SHARE during Hot Standby, simply by
>> making it same as normal SELECT, without any ill effects.
>
> True.
Actually, wait a minute. Why wouldn't we need to lock the tuples on
the s
+tools much more usable.
+
+
+
http://archives.postgresql.org/pgsql-committers/2010-06/msg00159.php
...Robert
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Thu, Jun 24, 2010 at 1:54 PM, Josh Berkus wrote:
> On 6/24/10 10:30 AM, Robert Haas wrote:
>> This part is no longer true:
>
> Right. And I just got an explanation of one of Oleg's patches. Let me
> submit a new doc patch if you haven't applied that one
On Thu, Jun 24, 2010 at 2:17 PM, Josh Berkus wrote:
> Robert,
>
> Updated patch.
I'm applying this now, with the following corrections:
- change tabs back to spaces
- revert incorrect change of guc-search_path to guc-search-path
> P.S. I hate CVS.
So don't us
On Thu, Jun 24, 2010 at 2:31 PM, Robert Haas wrote:
> On Thu, Jun 24, 2010 at 2:17 PM, Josh Berkus wrote:
>> Robert,
>>
>> Updated patch.
>
> I'm applying this now, with the following corrections:
>
> - change tabs back to spaces
> - revert incorrect cha
On Thu, Jun 24, 2010 at 4:59 PM, Simon Riggs wrote:
> On Thu, 2010-06-24 at 19:50 +0000, Robert Haas wrote:
>> Log Message:
>> ---
>> Some copy-editing of the Hot Standby documentation.
>>
>> Thanks to Joshua Tolley for the review.
>
> I rejected the
contrive a fight, you are mistaken. As for what it
would be best for me to spend my time on, I reserve the right to make
that decision myself. However, I have been known to take other
people's suggestions, including yours, when they are not presented as
an attack on the work in which I've
mention why pg_standby would not be suitable.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
privileges?
I don't see an obvious way to fit it in there, although it doesn't
seem like a bad idea. I also wonder if we should mention something in
the reference pages for GRANT and REVOKE - at least a cross-reference
to the correct section of the documentation.
--
Robert Haas
EnterpriseDB:
On Fri, Jul 2, 2010 at 5:28 PM, Bruce Momjian wrote:
> OK, everyone seems to like requiring dia.
I don't like it a bit. It's hard enough for people to build the docs as it is.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent v
On Fri, Jul 2, 2010 at 5:43 PM, Bruce Momjian wrote:
> Marc G. Fournier wrote:
>> On Fri, 2 Jul 2010, Robert Haas wrote:
>>
>> > On Fri, Jul 2, 2010 at 5:28 PM, Bruce Momjian wrote:
>> >> OK, everyone seems to like requiring dia.
>> >
>> >
of PostgreSQL, which of course isn't the case.
The tablespaces image labels the toplevel entity "PGCluster" but
doesn't use the "PG" prefix on any of the other items. That seems
inconsistent.
On the vacuum image, I don't know that the terms "active" and
s.
>
> Here is the PNG URL:
>
> http://momjian.us/expire/pgsql-docs/img/
>
> and the dia files:
>
> http://momjian.us/expire/pgsql-docs/dia/
Are these dia files generated by some other program, or did someone
really write all that XML by hand?
--
Robert Haa
a function like row_number()
> (not mentioned in other
> examples).
>
> I think at least the below three links should be added.
Committed. FWIW, it's easier to extract the patch (at least for me)
if you attach it rather than including it in the body of the email.
--
On Sat, Jul 3, 2010 at 6:48 PM, Thom Brown wrote:
> ..just an idea anyway.
Seems like a good one. But I'd still like to know the answer to the
question I asked upthread - how is anyone supposed to generate images
this way?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb
On Sat, Jul 3, 2010 at 7:14 PM, Tom Lane wrote:
> Robert Haas writes:
>> Seems like a good one. But I'd still like to know the answer to the
>> question I asked upthread - how is anyone supposed to generate images
>> this way?
>
> Hmm, judging from
> http://l
ation, they care that the system has two processes talking
> with each other and sending information between nodes. After testing SR,
> I can say that the secondary node generates wal files under pg_xlog when
> using SR.
I'm going to argue that diagrams should be made as technically correc
mprove /contrib/dblink's handling of dropped columns
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
ue in ~/.psqlrc was ignored by
>> psql -c "..." command but not by echo ""|psqlThought it was strange.
>> [...]
>
> Patch attached to clarify the latter.
Committed.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Com
On Fri, Jul 9, 2010 at 10:46 PM, Bruce Momjian wrote:
> PNG image attached.
Is it just me, or does that look pretty pixellated and awful?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.
1 - 100 of 297 matches
Mail list logo
