[pgpool-general: 3818] Re: Bug report response timeline
ishii at postgresql.org
Thu Jun 18 17:18:36 JST 2015
Ok, I created a patch trying to solve the problem. Could you please
try out the attached patch?
SRA OSS, Inc. Japan
> My personal preference is to never use spaces. However, as part of my company's product it allows customers to choose "class" names that are descriptive for them and easy to remember. This often times involves spaces. We sanitize the names and use them as part of the table names. Since spaces are not stripped as part of the sanitization process they remain in the table name. I completely agree with you that spaces are very unusual, but still they are allowed in postgres as long as you use double quotes.
> On Wed, Jun 17, 2015 at 11:44 AM, Tatsuo Ishii <ishii at postgresql.org>
>> Just out of curiosity, why do you want to use spaces for table names?
>> For me it is pretty unusual.
>> Best regards,
>> Tatsuo Ishii
>> SRA OSS, Inc. Japan
>> English: http://www.sraoss.co.jp/index_en.php
>>> I created a bug report here http://www.pgpool.net/mantisbt/view.php?id=136 but no one has been assigned or taken a look at it. Or at least thats what it seems. What is the general timeline for getting these resolved or at least responded to? Also if anyone has thoughts on how to resolve this issue that would be much appreciated. It's been 11 days so far.
>>> Essentially pgpool uses to_regclass() but when given a class name with a space, it uses single quotes and the to_regclass function fails. Despite my query using double quotes. More information is in the bug submission.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7788 bytes
Desc: not available
More information about the pgpool-general