On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane wrote:
> Bruce Momjian writes:
>> Tom Lane wrote:
>>> Bruce Momjian writes:
Perhaps we should allow any SVG file to be imported, but only allow
modifications by a single SVG editor.
>
>>> How is that sensible? The first change to the file will
Robert Haas wrote:
> On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane wrote:
> > Bruce Momjian writes:
> >> Tom Lane wrote:
> >>> Bruce Momjian writes:
> Perhaps we should allow any SVG file to be imported, but only allow
> modifications by a single SVG editor.
> >
> >>> How is that sensible?
On Mon, Jun 13, 2011 at 2:25 PM, Rafael Martinez
wrote:
> On Mon, 2011-06-13 at 13:24 -0400, Robert Haas wrote:
>> On Fri, Jun 3, 2011 at 3:42 AM, Rafael Martinez
>> >
>> > You can see the graph with the generation of WAL files + some extra
>> > information for this test here: http://folk.uio.no/r
On Mon, Jun 13, 2011 at 11:01 AM, Robert Haas wrote:
> On Thu, May 5, 2011 at 11:20 AM, Tom Lane wrote:
>> The documentation for ON_ERROR_STOP states, or at least implies by
>> omission, that it only affects the behavior in non-interactive scripts:
>>
>> By default, if non-interactive scri
On Tue, Jun 14, 2011 at 11:07 AM, Robert Haas wrote:
> Hearing no objections, committed.
s/variale/variable
Josh
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Robert Haas writes:
> Hearing no objections, committed.
Looking at this a second time, it needs spell-checked. "variale"?
regards, tom lane
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/m
On Tue, Jun 14, 2011 at 08:59:41AM -0400, Bruce Momjian wrote:
> Robert Haas wrote:
> > On Mon, Jun 13, 2011 at 8:46 PM, Tom Lane wrote:
> > >
> > > Or at least, somebody passes it through the "proper editor" before
> > > committing. ?As long as said editor can read SVG output from a
> > > reasona
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 03:01 PM, Robert Haas wrote:
> If you're interested in troubleshooting this
> further, I think you should post to pgsql-performance and try to get
> some help understanding what is happening. If we get to the point
> where we have a clea