Search Postgresql Archives

Re: wrong protocol sequence?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Sep 22, 2005, at 10:11 AM, Андрей wrote:

I'm sending such messages to server in native postgresql protocol: 'Parse' -> 'Describe' -> 'Sync' (get: 'Parse Complete' and 'Ready For Query' messages back). But when the sequence became: 'Parse' -> 'Sync' (get: 'Parse Complete' and 'Ready For Query' messages back), little pause, 'Describe' -> 'Sync' - server is crashing (error = memory can't be 'read')!

My query is as simple as possible 'select * from table_name'. What am I doing wrong?



I think I recall having some problems around this also. But I don't think there is any reason to need Parse -> Sync anyway. If you just want to prepare, use Parse -> Describe -> Sync. For executing, Parse (if not already parsed) -> Bind -> Describe -> Execute -> Sync.




John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
      choose an index scan if your joining column's datatypes do not
      match


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux