On 9 June 2010 03:48, Robert Haas wrote:
> Er, I should also say, thanks for the report, and please test. I am
> definitely not an expert on YAML.
>
I'm not an expert on YAML either, but I don't think this works (at
least it breaks against the online YAML parser here:
http://yaml-online-parser.a
On 09/06/10 17:14, Tom Lane wrote:
Robert Haas writes:
It's possible. I don't really see a reason not to add an = operator
for XML - does anyone else?
Yes, that was considered and rejected, IIRC. What is your definition
of equality for xml?
Yes - but in that previous discussi
On 5/26/10 7:18 PM, Joel Henrique wrote:
The following bug has been logged online:
Bug reference: 5475
Logged by: Joel Henrique
Email address: j...@cefet-al.br
PostgreSQL version: 8.4.4-1
Operating system: Windows 2003 Server
Description:Problem during Instalation
De
Robert Haas writes:
> It's possible. I don't really see a reason not to add an = operator
> for XML - does anyone else?
Yes, that was considered and rejected, IIRC. What is your definition
of equality for xml?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgs
On 9/06/2010 11:06 AM, Robert Haas wrote:
On Wed, May 26, 2010 at 9:48 AM, Joel Henrique wrote:
The following bug has been logged online:
Bug reference: 5475
Logged by: Joel Henrique
Email address: j...@cefet-al.br
PostgreSQL version: 8.4.4-1
Operating system: Windows 200
On 09/06/10 15:22, Robert Haas wrote:
On Thu, Jun 3, 2010 at 7:16 PM, Mark Kirkwood
wrote:
Maybe I gave this guy a bad title - is it a concern that the 'width'
estimate is so far off for xml datatypes (because of no = op)? It seemed to
me that this could result in some bad plan choices (e.
On Thu, Jun 3, 2010 at 7:16 PM, Mark Kirkwood
wrote:
> Maybe I gave this guy a bad title - is it a concern that the 'width'
> estimate is so far off for xml datatypes (because of no = op)? It seemed to
> me that this could result in some bad plan choices (e.g in subqueries etc).
It's possible. I
2010/5/26 MarceloG :
> Olá pessoal,
> no meu aplicativo, ao invés de tabelas temporárias, utilizo o pg_listener
> para verificar e impedir que o mesmo usuário acesse o sistema
> simultaneamente.
> Eu disparo um "notify usuario+código" e, a cada acesso, leio a tabela/
> catálogo pg_listener para sab
2010/5/25 carolina :
>
> The following bug has been logged online:
>
> Bug reference: 5473
> Logged by: carolina
> Email address: caro.herrer...@hotmail.com
> PostgreSQL version: postgresql 8.4
> Operating system: windows xp
> Description: problema para reinstalar postgr
On Wed, May 26, 2010 at 9:48 AM, Joel Henrique wrote:
>
> The following bug has been logged online:
>
> Bug reference: 5475
> Logged by: Joel Henrique
> Email address: j...@cefet-al.br
> PostgreSQL version: 8.4.4-1
> Operating system: Windows 2003 Server
> Description:
On Mon, Jun 7, 2010 at 5:33 PM, Greg Stark wrote:
> On Mon, Jun 7, 2010 at 5:36 PM, Piergiorgio Buongiovanni
> wrote:
>> I reused the previous command to re-set the sequence value to the right one,
>> but I see that the START value is now 59100. I reused the previous command
>> another time and t
On Tue, Jun 8, 2010 at 10:47 PM, Robert Haas wrote:
> On Mon, Jun 7, 2010 at 4:14 AM, Dean Rasheed wrote:
>> Testing 9.0 beta, I found that EXPLAINing certain queries in YAML
>> format will produce invalid YAML, for example:
>>
>> explain (format yaml) select * from foo where str_val = 'a: b';
>>
On Mon, Jun 7, 2010 at 4:14 AM, Dean Rasheed wrote:
> Testing 9.0 beta, I found that EXPLAINing certain queries in YAML
> format will produce invalid YAML, for example:
>
> explain (format yaml) select * from foo where str_val = 'a: b';
>
> The problem in this case is that a colon followed by whit
"Ovidiu Tanasiciuc" writes:
> I have 2 tables a and b
> a have column id - bigserial
> b have column Id - bigserial with I uppercase
> both automatic have 2 sequences
> the problem is then i make pg_dump with data only and insert command,even
> like or from pgadmin
> E:/Programe/PostgreSQL/8.4/bin
"Bakkiya" writes:
> We have postgresql 8.3.8 version on 32 bit and 64 bit SLES servers. On both
> the servers we are having the client encoding as UNICODE
> show CLIENT_ENCODING --- "unicode"
> We have created the database with UTF8 encoding.
> But when we give uppoer/lower of any extended charac
The following bug has been logged online:
Bug reference: 5494
Logged by: Ovidiu Tanasiciuc
Email address: tanasic...@yahoo.com
PostgreSQL version: 8.4.1
Operating system: Windows XP
Description:pg_dump dependiences sequence problem
Details:
I have 2 tables a and b
a
The following bug has been logged online:
Bug reference: 5493
Logged by: Bakkiya
Email address: bakk...@gmail.com
PostgreSQL version: 8.3.8
Operating system: Suse Linux 10
Description:Character Encoding is not happenning properly
Details:
Hi,
We have postgresql 8.3.
* Greg Smith:
> Florian Weimer wrote:
>> It has been claimed before that YAML is a superset of JSON, so why
>> can't the YAML folks use the existing JSON output instead?
>>
>
> Because JSON just crosses the line where it feels like there's so much
> markup that people expect a tool is necessary
18 matches
Mail list logo
