# Browse Column Sorting Slowness using PostgreSQL

**URL:** <https://clarionhub.com/t/browse-column-sorting-slowness-using-postgresql/6382>\
**Category:** questions\
**Tags:** postgresql, browse\
**Created:** [July 13, 2023, 2:37pm UTC](https://clarionhub.com/t/browse-column-sorting-slowness-using-postgresql/6382 "2023-07-13T14:37:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ThalesSilveirs](https://clarionhub.com/user_avatar/clarionhub.com/thalessilveirs/32/3642_2.png) [@ThalesSilveirs](https://clarionhub.com/u/ThalesSilveirs)\
**Post date:** [July 13, 2023, 5:43pm UTC](https://clarionhub.com/t/browse-column-sorting-slowness-using-postgresql/6382/2 "2023-07-13T17:43:50Z")

</div>

I had a significant improvement when I changed my command line there in the dictionary, adding as a forum colleague gave me an example, here it is:

> @seanh  
> `/BUSYHANDLING=2 /ISOLATIONLEVEL=2 /JOINTYPE='ODBC 3.0' /NESTING=TRUE `

> [@Any idea how Multiple Join with PostgreSQL?](https://clarionhub.com/t/any-idea-how-multiple-join-with-postgresql/6369/2):
>
> In a browse it should ‘Just Work’. I assume you mean putting it all in a SELECT with appropriate Joins? You might need a little extra on you dct definition. This is my standard for Postgres tables: /BUSYHANDLING=2 /ISOLATIONLEVEL=2 /JOINTYPE='ODBC 3.0' /NESTING=TRUE Note there is also a Windows ODBC Join limitation of 2 or 3 or something. So more complex stuff it’s better to put into a server side view Carl Barnes: Edit to add links to help for above parameters. /JoinType='ODBC …

---

_[View the full topic](https://clarionhub.com/t/browse-column-sorting-slowness-using-postgresql/6382)._