At least two other popular production database products provide true
serializability, as described in PostgreSQL documentation (section 12.2.2.1 of
8.1 devel). I'm a big fan of PosgreSQL, but let's not overstate things. Some
users may have applications with do depend on the true serializabilit
On this page:
http://www.postgresql.org/docs/8.1/interactive/sql-altertable.html
there is this user comment:
To change the data type of a column, do this:
BEGIN;
ALTER TABLE tab ADD COLUMN new_col new_data_type;
UPDATE tab SET new_col = CAST(old_col AS new_data_type);
ALTE
>>> On Wed, Mar 22, 2006 at 1:00 pm, in message
<[EMAIL PROTECTED]>, Robert Treat
<[EMAIL PROTECTED]> wrote:
>
> I believe Tom's comments in this email apply similarly here.
> http://archives.postgresql.org/pgsql- general/2006- 03/msg00891.php
The user comment's recommended technique includes t
Tom Lane wrote:
> Robert Haas writes:
>> Fujii Masao wrote:
>>> 3. Your proposal
>>>Treat superuser replication connection like non-superuser one
>
>> Well, only for this one very specific purpose. I would adjust
>> the docs like this:
>
>> Determines the number of connection "slots" that
Josh Berkus wrote:
> I believe that the note about needing fsync for Warm Standby to
> work correctly is true, but could someone verify it?
It couldn't really affect the archiving of the WAL files, but if your
warm standby is there for recovery purposes, it might not make a lot
of sense to tur
Marc Cousin wrote:
> DECLARE
> CURSOR referrer_keys IS
> I guess it should be
>
> DECLARE
> referrer_keys CURSOR IS
> If I'm right, a patch is attached (the code works with the
> correction)
The patch looks correct to me.
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@
In looking for documentation of pgcrypto to respond to a user
request for help, I noticed that we could have provided more links
to help users find the docs for it. Attached is a docs patch which
is intended to help with that.
-Kevin
*** a/doc/src/sgml/pgcrypto.sgml
--- b/doc/src/sgml/pgcrypto.
Robert Haas wrote:
> I don't think the index entry you've added to pgcrypto is very
> appropriate, considering that there is a section with *exactly
> that name* in runtime.sgml.
That was intentional. Did you look at what it generated on the
index page?
| encryption, Encryption Options
|
Thom Brown wrote:
> On 12 August 2010 00:05, Thom Brown wrote:
>> I noticed that there are 2 linked entries for "Privileges":
>> http://www.postgresql.org/docs/9.0/static/bookindex.html#AEN128982
>>
>> While they both go to different pages (with admittedly very
>> similar content), those pages ar
Thom Brown wrote:
> In response to a user asking a question about indexes on primary
> keys
>
(http://archives.postgresql.org/pgsql-performance/2010-08/msg00194.php)
> I attach a patch to add information to the Primary Keys section of
> the Constraints page. While the information already exists
Thom Brown wrote:
> Well I guess the question is: "where will most people first look
> to find that piece of information out?"
The OP mentioned looking in the Indexes section of the documentation
for the answer.
> As long as the information isn't digressing from the topic it's
> mentioned in
Thom Brown wrote:
> On 18 August 2010 21:53, Peter Eisentraut wrote:
>> On ons, 2010-08-18 at 16:52 +0100, Thom Brown wrote:
>>> I attach a patch to add information to the Primary Keys section
>>> of the Constraints page. While the information already exists
>>> on the CREATE TABLE, I don't th
Thom Brown wrote:
> And another prototype:
> http://www.flickr.com/photos/dark_ixion/4927669444/sizes/o/
Wow! That looks *really* slick!
That is much more readable than what I'm used to seeing!
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to you
Thom Brown wrote:
> Joshua D. Drake wrote:
>> It is great for it to be aesthetically pleasing but if we have
>> those minor inconsistencies I think it would be distracting from
>> the information itself.
>
> Agreed, and it's sort of experimental at the moment. If it
> doesn't help present inf
Thom Brown wrote:
> Kevin Grittner wrote:
>> It looks like discussion died here. Do you want to propose a new
>> patch? (I'd be happy to give it a shot if you'd rather.)
>
> Sure, go for it. :)
Initial stab at it attached.
I'm torn on whether the
Thom Brown wrote:
> Looks good. Do we usually got into fine details such as the name
> of the index? They'll see the index name returned when they
> create the table or add the constraint anyway, and if they missed
> it they only need to do a "\dt tablename" to find out what it was.
Hmmm...
Thom Brown wrote:
> Yeah, I think that covers it well. :)
I found a typo. :-( Another revision attached.
-Kevin
*** a/doc/src/sgml/ddl.sgml
--- b/doc/src/sgml/ddl.sgml
***
*** 550,555 CREATE TABLE products (
--- 550,560
+ Adding a unique constraint
Thom Brown wrote:
> The reason I removed the corners is that they can't be applied to
> a warning or caution box using their current markup (as the
> background pushes beyond the rounded corner), and when they appear
> near a normal rounded-corner box, it might look a bit inconsistent
> (same bu
Thom Brown wrote:
> Okay, got rid of all the shadows, rounded corners etc and made
> some other changes:
> http://www.flickr.com/photos/dark_ixion/4932396780/sizes/o/
I generally liked the rounded corners. The tables near the front
are probably better off without them, but I would rather see
Alvaro Herrera wrote:
> Excerpts from Thom Brown's message:
>> variance(> class="parameter">expression)
>>
>> vs
>>
>> stddev_samp(> class="parameter">expression)
>>
>> Which way is correct?
>
> The latter I think -- see
> http://www.docbook.org/tdg/en/html/function.html
> (but perhaps searc
Thom Brown wrote:
> Okay, as per Robert's suggestion, I've changed all
> example/definition/synopsis boxes to grey, and followed Dave's
> suggestion of restoring borders and making the default text colour
> black for all boxed content. Bear in mind the rubbish screenshot
> app I'm using heavily
Thom Brown wrote:
> Kevin Grittner wrote:
>> You find examples like this:
>>
>>
>>
>> void qsort
>>void *dataptr[]
>>int left
>>int right
>>int (* comp)
>> void *, void *
>>
>>
>>
>
Thom Brown wrote:
> The only change is the addition of very light shadowing (for Dave
> and Kevin)
Sorry for sounding picky, but can the shadowing be even lighter? It
seems a tad heavy next to the light gray in the boxes.
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.o
Tom Lane wrote:
> The yellow "note" boxes still strike me as too eye-grabbing for
> their purpose. Otherwise this version seems nice.
How about a color which still differentiates these without being
quite so bold -- like Beige (#F5F5DC)?
For an example, see:
http://en.wikipedia.org/wiki/B
Thom Brown wrote:
> Kevin Grittner wrote:
>> The rounded corners and shadows aren't showing up in Konqueror
> Okay, it appears there's also a KHTML engine setting for pre-CSS3
> support. I've added that in now for rounded corners and shadows.
> Any differe
Thom Brown wrote:
> And Kevin, I made the shadows a bit lighter in this version and
> used the beige notes box.
For my taste, that's perfect. (Now there's the trivial matter of
making everyone else happy. ;-) )
The rounded corners and shadows aren't showing up in Konqueror, but
everything
Thom Brown wrote:
> Okay, I've made a couple other changes, but if it's not working
> now, I don't think it's supported. This page suggests that
> box-shadow isn't yet supported by KHTML:
> http://www.legendscrolls.co.uk/webstandards/khtml
No shadows in Konqueror.
> I've just tested it in O
Thom Brown wrote:
Thom Brown writes:
> Now the font sizes should be virtually the same in all
> browsers.
That looked good in Firefox and Konqueror on my kubuntu machine.
> Okay, I've added a slightly modified version of that in (was
> missing in the new version of the site), r
Thom Brown wrote:
> Bruce Momjian wrote:
>> I found some sample code the is supposed to work in all browers.
>> I tested it in Firefox and it worked. It should work in Opera
>> and IE as well. HTML/Javascript file attached.
>
> Thanks Bruce. I've implemented your recommended change. :)
L
Thom Brown wrote:
> I've added an experimental content navigation menu (appears in
> top-right-hand corner) which jumps to sections of the same page.
> It only appears on pages which have items to navigate to,
> including the main index.
I don't feel strongly about this feature one way or ano
Thom Brown wrote:
> Anymore feedback/suggestions? Anything not look right? Are we there
> yet?
The only thing I found a little distracting with the current layout
is that on some pages the horizontal lines for the section and
subsection are very close together. If the lines for subsections
we
Thom Brown wrote:
> Kevin Grittner wrote:
>> The only thing I found a little distracting with the current
>> layout is that on some pages the horizontal lines for the section
>> and subsection are very close together. If the lines for
>> subsections were less impos
Thom Brown wrote:
> The notes section still looks really drab on my screen.
Are you talking about the Release Notes page:
http://pgweb.darkixion.com:8081/docs/8.4/static/release.html
notes for a major release:
http://pgweb.darkixion.com:8081/docs/8.4/static/release-8-4.html
or notes fo
Thom Brown wrote:
> There are boxes containing notes which I had originally coloured
> yellow, but we went for beige instead. Example appears on:
> http://pgweb.darkixion.com:8081/docs/9.0/static/ddl-priv.html
Oh, *those* notes. Got it.
As I recall, Tom felt that the yellow was too much of
"Erik Rijkers" wrote:
> Something seems to have gone wrong with generating the version 9.0
> PDFs on the website: both A4 and US have no bookmarks tab. (I'm
> reading with Adobe Reader 7.0.0)
Odd. From this page:
http://www.postgresql.org/docs/manuals/
With Okular Version 0.9.2 the 9.0
Katharina kuhn wrote:
> I'd like to build a custom text search parser and then use it
> within a custom text search configuration.
> It would be great if you could give us an example showing how to
> build a custom parser, including examples of start, gettoken and
> end functions.
You might wa
I was reviewing the Concurrency Control chapter to work up
suggestions for the guy who has agreed to create a doc patch to go
with the Serializable Snapshot Isolation (SSI) patch. It occurred to
me that there is a gap which has nothing to do with the patch, and
wondered whether we should ignore it,
"Kevin Grittner" wrote:
> The issue is that I don't see anything in the documentation which
> would lead people to expect the following behavior
Never mind, the "website" example covers the ground. I shouldn't try
to post before the caffeine is fu
Thom Brown wrote:
> I've attached a couple minor fixes to the docs. One relating to
> SECURITY LABEL and the other for pg_class.relpersistence
relpersistence should be "char", not char.
Oddly enough, there is a difference.
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.
Thom Brown wrote:
> relkind in the same table is the same type, but isn't displayed as
> "char" in the docs, and the same applies to many other system
tables.
> They would need changing too then.
>
> Examples are:
>
> pg_type.typtype
> pg_proc.provolatile
> pg_attribute.attstorage
That's a g
Bruce Momjian wrote:
> A private email I received indicated that our documentation about
> ignoring trailing spaces in CHAR() comparisons was slightly
> inaccurate. I have update our docs to indicate it is only
> non-pattern comparisons that ignore spaces with CHAR(). Applied
> doc patch attac
Bruce Momjian wrote:
> I have applied an updated patch
FWIW, that looks good to me.
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Bruce Momjian wrote:
> Peter Eisentraut wrote:
>> On tis, 2011-03-08 at 22:32 -0500, Bruce Momjian wrote:
>>> Looking at our ref pages, I see some manual pages specify long
>>> options that take arguments using '=', e.g. initdb.sgml:
>>>
>>> --long-opt=opt
>>>
>>> and some do not, e.g. pg_du
Trivial patch attached.
-Kevin
ssi-typo-20110327.patch
Description: Binary data
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Daniele Varrazzo wrote:
> - http://pgmp.projects.postgresql.org/highlight/psql.html
> - http://pgmp.projects.postgresql.org/highlight/postgres.html
>
> Is there any interest in applying highlighted syntax to the html
> rendering of the manual?
When using an editor I like some color highlighti
Jack Douglas wrote:
> There are two kinds of people on this earth, those who understand
> boolean arithmatic and those who don't. I'm not one of them.
Hmmm... From that, I don't know if you do. Which do I record in the
understands_boolean column of the database record for you? Dang, I
knew
Peter Eisentraut
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
Ferdian Zaman wrote:
>
Did you try visiting the web page mentioned in the post to which
you replied? If so, did you have a problem unsubscribing? If so,
please describe what happene
Satoshi Nagayasu wrote:
> I think it should be rewritten as following:
> -
> If the query returns more than one records, multiple linked
> SQLDA structures are returned, and desc_next
> holds a pointer to the next element (record) in the li
Robert Haas wrote:
> Grzegorz Szpetkowski wrote:
>> "The join condition specified with ON can also contain conditions
>> that do not relate directly to the join."
I think the trouble starts with that sentence, which I believe to be
completely false and misleading.
Simplifying a real-life inst
Alvaro Herrera wrote:
> Except that we don't use the first person in docs, do we?
find doc/src/sgml -name '*.sgml' | xargs cat | egrep -ci '\bwe\b'
786
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mai
"Albert Ward" wrote:
> I am interested in your publication
> http://www.postgresql.org/docs/8.1/static/kernel-resources.html
> and would like to translate it to Bulgarian language, so I can
> share it with the readers on my blog. For doing that I need your
> written permission.
If you follow
Henry Drexler wrote:
> "If the results of the first argument are null, it will return the
> second."
Unless the second is also null, in which case it will return the
third. Unless the third is also null...
The trick is to come up with language which recognizes that there
can be any number o
Josh Berkus wrote:
> What packages and versions do I need to install to build the docs
> on Ubuntu?
>
> I tried 10.04's version of Openjade, which wasn't recognized
> Requirements for building the docs are not documented in our docs.
I did find that getting the doc build going was a bit fus
"Holec, JPH Software" wrote:
> pg_read_file('pg_log... gives me this report and 0xe86974 doesn't
> know Google...
It would be an odd web page which listed all the values which are
not valid as character encodings in any particular encoding scheme.
> Can You help me?
Questions like this bel
antonio guerra wrote:
> why all postegresql manuals are not readible?
> If I try to open it it says me "file is corrupted and it is
> impossible to repair it".
What URL(s)?
-Kevin
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://ww
[Please keep the list copied.]
> antonio guerra wrote:
> Il 28/03/2012 22.12, Kevin Grittner ha scritto:
>> antonio guerra wrote:
>>> why all postegresql manuals are not readible?
>>> If I try to open it it says me "file is corrupted and it is
>>>
antonio guerra wrote:
> Il 29/03/2012 14.03, Kevin Grittner ha scritto:
>> [Please keep the list copied.]
"Reply All" works on most email products.
>> antonio guerra wrote:
>>>
http://www.postgresql.org/files/documentation/pdf/9.1/postgresql-9.1-A4.pdf
&
Thom Brown wrote:
> I noticed that "pl/py" is listed on the procedural languages page
> under external projects, and upon following the link, I can't see
any
> mention of a procedural language.
At the bottom/left corner of the linked page was a link to here:
http://python.projects.postgresql
Thom Brown wrote:
> Kevin Grittner wrote:
>> Thom Brown wrote:
>>
>>> I noticed that "pl/py" is listed on the procedural languages
>>> page under external projects, and upon following the link, I
>>> can't see any mention of a procedura
Florence Cousin wrote:
> At the bottom of the page about Date/Time types (
>
http://www.postgresql.org/docs/9.1/interactive/datatype-datetime.html
> )
> there is this sentence :
>
> Date conventions before the 19th century make for interesting
> reading, but are not consistent enough to warrant
[I had a bit of trouble picking which list to use; I guess Wiki
pages are part of our docs, in a way...]
How do people feel about "TL;DR:" being used at the start of a Wiki
page to which we want to direct users?
http://wiki.postgresql.org/wiki/Guide_to_reporting_problems
I'll go first -- I ha
> "Kevin Grittner" writes:
>> How do people feel about "TL;DR:" being used at the start of a
>> Wiki page to which we want to direct users?
Tom Lane wrote:
> I think it's a pretty lousy way to start off this page in
> particular; way too flipp
Marcelo Sena wrote:
> So, is it documented somewhere?
http://www.postgresql.org/docs/current/static/tutorial-transactions.html
| PostgreSQL actually treats every SQL statement as being executed
| within a transaction. If you do not issue a BEGIN command, then
| each individual statement has
liu...@neusoft.com wrote:
> I am a programmer, and i want to use Postgresql 9.2.2 to store my
> applications' data. I had to
> build a trigger wich based on Database level( When the database startup
> , this trigger will fired and
> executed.),while i found there are not defined database-level t
Lyle wrote:
> Is there other documentation available that covers this?
You might want to read this page:
http://www.postgresql.org/docs/9.2/static/storage-toast.html
Note that there is seldom a good reason to use char(n) in
PostgreSQL for any value of n. As the page you cited mentions,
"While c
hem alone, but would be a felony.
> But I'm not going to object to simply removing the entire sentence.
I don't know -- it seems like the reasons for the feature are
non-obvious enough that such a note is useful.
--
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Ent
how to go about making changes in
> a way that would be considered useful.
Your best bet would be to download the source code from here:
http://www.pgadmin.org/development/git.php
... and submit context diff patches to the pgadmin-hackers list.
The pgsql-* lists are not really the right pl
s is to copy to a different name or directory and mv the file
into place once it is complete -- or use software which does that
automatically, like rsync does.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgs
Josh Berkus wrote:
> On 08/11/2014 10:21 AM, Kevin Grittner wrote:
>>> Is there some good reason why "test ! -f" was added to the
>>> sample?
>>
>> In an environment with more than one cluster archiving, it is
>> otherwise way too easy to copy a
WAL stream to a hot
standby. Last I checked (which was admittedly at least a couple
years back) there was no such utility, although I seem to remember
that Magnus had done some work that looked like it could be bent to
that end.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Ente
Magnus Hagander wrote:
> On Wed, Aug 13, 2014 at 11:23 PM, Kevin Grittner wrote:
>
>> The above is regarding WAL file archiving -- I'm not putting down
>> streaming replication. Of course, what I would have *really* liked
>> is a WAL receiver that could write out
resulting
sentences need to be compared to see which is more clear and
concise.
> * "newly-received" -> "newly received"
> * "recently-used" -> "recently used"
I think these depend on context. To me, the former scans better
when the comb
rated from any following text by punctuation
-- usually a comma.
In patch 0003- I agree that the change to "exactly the same" reads
better. I'm torn on changing the hyphens to spaces. I probably
wouldn't change them, but I wouldn't squawk if others preferred to
do so.
Marti Raudsepp wrote:
> Kevin Grittner wrote:
>> For the initial patch, I agree with all except the first change of
>> "others'" to "other's" -- the start of the sentence uses "All", so
>> there is clearly more than one &quo
ar errors
makes enough of a dent in what is needed to be worth it.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Alvaro Herrera wrote:
> One reasonably-serious page
... and with that, I guess you've expressed a reasonably clear
preference. ;-)
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
d to go back
over it one or two extra times to make sure I'm understanding.
There's at least one place I spotted "e.g." where it seemed to me
that the "example" was really a restatement in other terms, so it
seemed like it should have been "i.e." -- I w
J Connolly wrote:
> I still think being on github would lower the barrier to entry
> for would-be contributors
I'm not sure whether you're unaware of the github mirror or want
something different:
https://github.com/postgres/postgres
--
Kevin Grittner
EDB: http://www.ente
ore harm than good. Even those citing the paper
by Berenson, et al., often miss the text in *that* paper about what
the actual definition of serializable transactions in the standard
is, and instead focus on the quick-to-read tables of how the
misinterpretation of serializable transactions based on the
standard's table of phenomena (which the paper dubs "ANOMALY
SERIALIZABLE") differs from truly serializable behavior.
People do love tables like this, which makes providing them
tempting; but when a short, clean table is available they often
seem less inclined to take the trouble to read the real information
the table summarizes -- and they come away with distorted and
incorrect ideas about the subject matter.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
having two separate lines
> was cleaner.
I think one row per transaction isolation level, with three
possible values per cell, would be the cleanest. I have been
trying to think of alternatives for the three values, but have not
come up with anything better than David's suggestion.
-
Bruce Momjian wrote:
> On Sat, Apr 25, 2015 at 07:45:35PM +0000, Kevin Grittner wrote:
>> We could perhaps have the column header say "Non-Serializable
>> Behavior" or some such; but I think we need to define whatever
>> term we use for the new column header.
>
possible orderings of running those
transactions one at a time.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Bruce Momjian wrote:
> updated:
>
> http://momjian.us/expire/transaction-iso.html
I can't think of any way to improve on that.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresq
't
link to Wiki pages and the example is somewhat long to include
in-line in the documentation. Any thoughts on the best solution to
that?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Sunday, November 1, 2015 7:59 PM, Craig Ringer wrote:
> The explicit locking docs mention the lock taken by REFRESH
> MATERIALIZED VIEW CONCURRENTLY, but not plain REFRESH MATERIALIZED
> VIEW. Patch.
Pushed, with minor adjustment.
--
Kevin Grittner
EDB: http://www.enterprised
ror message.
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
It's not really a question of whether we should go back to
documenting the deprecated syntax, but whether (and when) support
for it should finally be ripped out. It was last documented in 8.4.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent
> that statement is no longer true if I understand the documentation
> correctly. Here's a brief patch to tweak that sentence.
Pushed. Thanks!
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@p
ded in favor of omitting the hyphenation in such cases.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
On Tue, Jun 7, 2016 at 8:22 AM, Dmitry Igrishin wrote:
> 2016-06-07 15:44 GMT+03:00 Kevin Grittner :
>> On Tue, Jun 7, 2016 at 6:26 AM, Dmitry Igrishin wrote:
>>
>>> In "Internal position: this is defined the same as the P field, but it
>>> is used
ng the
problem, and provide a detailed dump of memory contexts (with
allocated space in each). Other connections are generally
unaffected and the cause of the problem can be fixed to prevent
recurrence.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
* form is bytea; those functions *return* text and
are thus not a good way to get back to unencrypted bytea data; an
additional transformation would still be required to get to the
byte format from text, and the bytes representing those character
strings would depend on the character encoding.
--
Ke
Current behavior seems harmless and possibly useful to me, but it
seems marginal enough I wouldn't care if the change from READ WRITE
to READ ONLY was also prohibited.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
plosion needed.
If you value the data in your database you should assume that the
OS could go down at any instant without proper shutdown, and that
your storage system(s) could be lost without warning at any time.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Comp
On Wed, Nov 23, 2016 at 2:12 PM, Gunnar "Nick" Bluth
wrote:
> Am 23.11.2016 um 20:21 schrieb Kevin Grittner:
>> On Wed, Nov 23, 2016 at 12:24 PM, Gunnar "Nick" Bluth
>> wrote:
>>> to get actual _data loss_, you'd have to have a power outage
ight question whether the benefit
was worth the effort of adding it.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
96 matches
Mail list logo
