[prev in list] [next in list] [prev in thread] [next in thread]
List: postgis-users
Subject: Re: [postgis-users] Raster Table Name With Upper-Case Characters
From: Osahon Oduware <osahon.gis () gmail ! com>
Date: 2018-03-21 15:27:10
Message-ID: CAGpiUSixKi=KOSe_H2GinU1MLew_+ebF8Q+zXNWbUhet+ghqFQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Hi,
As a follow-up on this subject, I want to point out something 'strange' I
discovered with Rasters using mixed-case (lowercase and uppercase) in the
table names - QGIS takes like forever to load them. Whereas Rasters with
lowercase table names (that are loaded with the same parameters/options as
those with mixed-case table names using the raster2pgsql tool) load very
fast on QGIS.
Has anyone had similar experience? Can someone explain why this great
difference in performance between mixed-case and lowercase raster table
names and any possible workarounds. The preference for my project is
mixed-case raster table names.
*NB:* You need to test with a fairly large raster set to determine the
performance difference.
On Fri, Jul 14, 2017 at 1:47 PM, Osahon Oduware <osahon.gis@gmail.com>
wrote:
> Hi Mateusz,
>
> I agree with you. Thanks a lot.
>
> On Fri, Jul 14, 2017 at 1:36 PM, Mateusz Loskot <mateusz@loskot.net>
> wrote:
>
>> On 14 July 2017 at 14:27, Osahon Oduware <osahon.gis@gmail.com> wrote:
>> > Hi Mateusz,
>> >
>> > I have just tried using the -q option and it works. Thanks a lot. I have
>> > gone through the doc a lot to resolve several issues in the past. In
>> this
>> > case it was an oversight as I thought that explicitly wrapping the
>> > identifiers in quote would give the same result as the -q option.
>>
>> raster2pgsql is modelled after shp2pgsql, in terms of capabilities,
>> so you shouldn't need any quoting/escaping gymnastics to tell the loaders
>> what case of names you want.
>>
>> It might have been easier if raster2pgsql used -k as shp2pgsql does,
>> but -k is taken by different option.
>>
>> raster2pgsql docs on -q could have been clearer though.
>> Patches are welcome.
>>
>> Best regards,
>> --
>> Mateusz Loskot, http://mateusz.loskot.net
>> _______________________________________________
>> postgis-users mailing list
>> postgis-users@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/postgis-users
>>
>
>
[Attachment #5 (text/html)]
<div dir="ltr"><div><div><div>Hi,<br><br></div>As a follow-up on this subject, I want \
to point out something 'strange' I discovered with Rasters using mixed-case \
(lowercase and uppercase) in the table names - QGIS takes like forever to load them. \
Whereas Rasters with lowercase table names (that are loaded with the same \
parameters/options as those with mixed-case table names using the raster2pgsql
tool) load very fast on QGIS.<br><br></div>Has anyone had similar experience? Can \
someone explain why this great difference in performance between mixed-case and \
lowercase raster table names and any possible workarounds. The preference for my \
project is mixed-case raster table names.<br><br></div><b>NB:</b> You need to test \
with a fairly large raster set to determine the performance difference.<br></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 14, 2017 at 1:47 PM, \
Osahon Oduware <span dir="ltr"><<a href="mailto:osahon.gis@gmail.com" \
target="_blank">osahon.gis@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div>Hi Mateusz,<br><br></div>I agree with \
you. Thanks a lot.<br></div><div class="HOEnZb"><div class="h5"><div \
class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 14, 2017 at 1:36 PM, \
Mateusz Loskot <span dir="ltr"><<a href="mailto:mateusz@loskot.net" \
target="_blank">mateusz@loskot.net</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><span>On 14 July 2017 at 14:27, Osahon Oduware <<a \
href="mailto:osahon.gis@gmail.com" target="_blank">osahon.gis@gmail.com</a>> \
wrote:<br> > Hi Mateusz,<br>
><br>
> I have just tried using the -q option and it works. Thanks a lot. I have<br>
> gone through the doc a lot to resolve several issues in the past. In this<br>
> case it was an oversight as I thought that explicitly wrapping the<br>
> identifiers in quote would give the same result as the -q option.<br>
<br>
</span>raster2pgsql is modelled after shp2pgsql, in terms of capabilities,<br>
so you shouldn't need any quoting/escaping gymnastics to tell the loaders<br>
what case of names you want.<br>
<br>
It might have been easier if raster2pgsql used -k as shp2pgsql does,<br>
but -k is taken by different option.<br>
<br>
raster2pgsql docs on -q could have been clearer though.<br>
Patches are welcome.<br>
<div class="m_-7502236353827715875HOEnZb"><div class="m_-7502236353827715875h5"><br>
Best regards,<br>
--<br>
Mateusz Loskot, <a href="http://mateusz.loskot.net" rel="noreferrer" \
target="_blank">http://mateusz.loskot.net</a><br> \
______________________________<wbr>_________________<br> postgis-users mailing \
list<br> <a href="mailto:postgis-users@lists.osgeo.org" \
target="_blank">postgis-users@lists.osgeo.org</a><br> <a \
href="https://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" \
target="_blank">https://lists.osgeo.org/mailma<wbr>n/listinfo/postgis-users</a></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
[Attachment #6 (text/plain)]
_______________________________________________
postgis-users mailing list
postgis-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/postgis-users
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic