Обсуждение: postgresql query string length limit
I found any query exceeds 4096 charactors will be pruned automatically. i am wondering which knob should i change to make it larger , say, 10000 charactors. i searched for a while but was not able to find it online. so if anyone has a quick nswer that will be highly appreciated.
uwcssa <uwcssa@gmail.com> writes: > I found any query exceeds 4096 charactors will be pruned automatically. i am > wondering which knob should i change to make it larger , say, 10000 > charactors. i searched for a while but was not able to find it online. so if > anyone has a quick nswer that will be highly appreciated. Either you're using a very very old version of PostgreSQL, or a very crappy client library--there hasn't been a query length limitation in the server or in libpq for a long time (I think when there was one it was 8K by default). -Doug
I am using version 8.0.3. i installed using the --without-readline option. is there a quick workaround? On 2/19/06, Douglas McNaught <doug@mcnaught.org> wrote: > uwcssa <uwcssa@gmail.com> writes: > > > I found any query exceeds 4096 charactors will be pruned automatically. i > am > > wondering which knob should i change to make it larger , say, 10000 > > charactors. i searched for a while but was not able to find it online. > so if > > anyone has a quick nswer that will be highly appreciated. > > Either you're using a very very old version of PostgreSQL, or a very > crappy client library--there hasn't been a query length limitation in > the server or in libpq for a long time (I think when there was one it > was 8K by default). > > -Doug >
uwcssa <uwcssa@gmail.com> writes: > I am using version 8.0.3. i installed using the > --without-readline option. What client are you using? > is there a quick workaround? The limit shouldn't be there. If you can post a test case that demonstrates the problem, perhaps someone can help. -Doug
uwcssa wrote: > I am using version 8.0.3. i installed using the > --without-readline option. > Platform and os version would be good too :-), along with the client you are using to elicit this behavior (e.g, psql, Pgadmin etc). Cheers Mark
i am using psql client. On Fedora core (linux core: 2.4.20-8 ) as well on Suze 10.0 (core: 2.6.13-15.7-smp). Both has the same problem. thanks /19/06, Mark Kirkwood <markir@paradise.net.nz> wrote: > uwcssa wrote: > > I am using version 8.0.3. i installed using the > > --without-readline option. > > > > Platform and os version would be good too :-), along with the client you > are using to elicit this behavior (e.g, psql, Pgadmin etc). > > Cheers > > Mark > > > >
uwcssa <uwcssa@gmail.com> writes: > i am using psql client. On Fedora core (linux core: 2.4.20-8 ) > as well on Suze 10.0 (core: 2.6.13-15.7-smp). Both has the same problem. Please send a test case (shell script that shows the behavior). I can do $ psql -f foo.sql doug where 'foo.sql' inserts an 16384-character string into a table in a single query. This is with PG 8.0.4. The limit clearly does not exist, so we need to find out what you're doing wrong. :) -Doug
On Mon, Feb 20, 2006 at 01:28:50PM +1300, Mark Kirkwood wrote: > uwcssa wrote: > >I am using version 8.0.3. i installed using the > >--without-readline option. > > Platform and os version would be good too :-), along with the client you > are using to elicit this behavior (e.g, psql, Pgadmin etc). Are you cutting and pasting from one window into another? If so then I wonder if something like the terminal's buffer size is the problem. -- Michael Fuhr