On 2010-06-10, Robert Haas wrote:
> On Thu, Jun 10, 2010 at 9:02 AM, Stefan Kaltenbrunner
> wrote:
>> I for myself would be rather annoyed if we started quoting all column names
>> in our dumps. This is seriously hampering readability and while it is
>> already annoying that pg_dump output is slig
On 2010-06-10, Stefan Kaltenbrunner wrote:
> Tom Lane wrote:
>> Heikki Linnakangas writes:
>>> On 10/06/10 16:21, Robert Haas wrote:
I do agree that the human readability of pg_dump is an asset in many
situations - I have often dumped out the DDL for particular objects
just to look
The following bug has been logged online:
Bug reference: 5499
Logged by: Curtis Stecke
Email address: cste...@interlegis.com
PostgreSQL version: 8.4
Operating system: Windows Xp
Description:SQL syntax bug
Details:
Inserting text that starts with or ends with a dolla
"Curtis Stecke" wrote:
> Inserting text that starts with or ends with a dollar sign ($) is
> impossible. Documentation is not clear on how to do this as well.
Works for me. Care to give an example of your problem?
test=# create table t1 (c1 text);
CREATE TABLE
test=# insert into t1 values (
Top posting, sorry for that.
--
dim
Le 10 juin 2010 à 03:40, Robert Haas a écrit :
On Wed, Jun 9, 2010 at 9:35 PM, Bruce Momjian
wrote:
Robert Haas wrote:
I think users would rather have the restore fail, and know right
away
they have an issue, than to do the upgrade, and find out lat
On Fri, Jun 11, 2010 at 2:46 PM, Dimitri Fontaine
wrote:
Eeh, I've had this happen to me on earlier releases, and it didn't
feel like a feature to me. YMMV, of course.
>>>
>>> Would you have preferred later application failure?
>>
>> YES! It's a heck of a lot easier to fix the applicat
Stephen Frost writes:
> If it's an option w/ a default of "off", then chances are the admin will
> get the failure you're talking about, realize there's an issue, but then
> have a way to actually *fix* the restore without having to hack up
> multi-gigabyte files using vi. If you'd like, you're w
The following bug has been logged online:
Bug reference: 5500
Logged by: Robert Walker
Email address: robwalke...@speedymail.org
PostgreSQL version: 9.0 beta 2
Operating system: Windows XP 32-bit SP2
Description:SPI_execute_plan_with_paramlist SPI_ERROR_TRANSACTION
wi
Robert Haas writes:
> Suppose I have a server running 8.2 and I'm going to wipe it and
> install the latest version of $DISTRIBUTION which bundles 8.4.
[...]
> I'm sure someone will tell me my system administration practices suck,
> but people do these kinds of things, in real life, all the time.
"Robert Walker" writes:
> SPI_execute_plan_with_paramlist seems to be newly introduced into 9.0 beta
> that is causing an error in pl/pgsql when attempting to create a savepoint.
> This did not happen when using version 8.4 (which I assume was not using
> SPI_execute_plan_with_paramlist), so I bel
Excerpts from Robert Walker's message of vie jun 11 14:49:03 -0400 2010:
> SPI_execute_plan_with_paramlist seems to be newly introduced into 9.0 beta
> that is causing an error in pl/pgsql when attempting to create a savepoint.
> This did not happen when using version 8.4 (which I assume was not u
The following bug has been logged online:
Bug reference: 5501
Logged by: Dave Jarvis
Email address: thanga...@gmail.com
PostgreSQL version: 8.4.4
Operating system: Linux
Description:PostgreSQL JDBC Driver has inappropriate import
Details:
PROBLEM
postgresql-jdbc-8.4
12 matches
Mail list logo
