Re: [GENERAL] Why PGSQL has no developments in the .NET area?

2011-10-03 Thread Dusan Misic
I do not understand what you mean by the term sluggish?

Every .NET driver has some overhead when you first load it, and then it is
being cached into memory.

I have used Npgsql and it worked great for me.

If you are not satisfied with Npgsql, try Devarts connector.
On Oct 2, 2011 5:33 AM, Rohit Coder passionate_program...@hotmail.com
wrote:

 PgSQL has just one old NPGSQL driver for .NET, which is itself sluggish.
The ODBC driver works better as compared to NPGSQL, but I suspect the ODBC
driver is not the right choice for ORM framework of .NET.

 I want to know whether there is any efficient .NET provider and is PGSQL
compatible with the .NET entity framework.

 Regards,
 Rohit.



Re: [GENERAL] FREE hosting platforms with PostgreSQL, Java SDK, Tomcat, ecc.?

2011-08-06 Thread Dusan Misic
Please, behave nice and stick to the subject.

Mailing list is not the place for this kind of talk.

Sincerely,

Dusan


On Sat, Aug 6, 2011 at 9:22 PM, Fernando Pianegiani 
fernando.pianegi...@gmail.com wrote:

 Dear David, Nicklas,

 I think that this is not the right place where to discuss about this topic,
 but I have to try to give you an answer.

 PostgreSQL is not only open source, like MySQL is, but also free. This
 means that people who don't develop neither a line of code of PostgreSQL (or
 just some few lines of it) can use it to do what they want, even money,
 without having the obligation to provide back 1 cent to the PostgreSQL
 community. That's incredible I know, but it is so. And why? I don't know
 exactly, but I know that there are several reasons that are not very
 transparent. I can try to give my interpretation hopping that it is the
 real one or in any case thinking that it should be the correct one. If
 people who develop PostgreSQL make it free, people who don't develop
 PostgreSQL but who use it for their research projects or business can make
 available the results of their projects also to the developers of
 PostgreSQL, but overall to the worldwide community. And so, in case for
 example a developer of PostgreSQL or any other person should have a health
 problem, he can hope that his hospital uses the results of a research
 project got also with the help of PostgreSQL or of some other free
 technology.

 I think the previous one is the philosophy that should be behind the words
 open source and free. In all the other cases there are in my opinion
 interests that should be better clarified.

 If we do something for free for other people, then they can do something
 for other people using for free our results, and so on...the alternatives
 are under our eyes, that is the jungle of the market and the worldwide
 crisis. So David, don't worry for my activity of research, instead you
 should be seriously preoccupied if you do business. Moreover, the fact that
 my project ended could be in case an additional problem for both of us and
 not only if we should have problems of health strictly inherent to the
 results of research coming from a possible development of my old project.
 Obviously, I hope no for all of us. :-)

 David, Nicklas, if you make money by using PostgreSQL and you want to be
 really honest (as you claim honesty from me and from my work activity),
 please count that money and give the right percentage of it to the
 PostgreSQL community, but considering also who spent more time, resources
 like electric power, computer hardware, etc. than the others in developing
 it. In this way if you develop PostgreSQL, then you too can get your right
 percentage from you and from the other developers.

 Dear Scott, Niklas, you are right, the components and the resources
 necessary to manufacture the solutions developed within the arduino project
 are not for free. Only the schematics, the gerbers, etc. are for free.

 Finally, the world is full of companies that make available for free their
 hardware/software/human resources. Probably also you use them every day for
 free (e.g., the media in general) or you store your data for free in part of
 those resources (facebook, youtube, just to do general examples), but those
 resources are not really for free, those companies find the way to gain a
 lot of money with the fact that you access to their resources.

 In any case, excuse me if I have hurted your's feelings. My intention was
 not to ask for a free hosting platform (free stuff, etc.) to the PostgreSQL
 community, but I simply asked if the community knows anybody who provides a
 service of free hosting, supposing that in some way the provider of that
 hosting service would have earned his right income from me in some way (e.g.
 a banner installed on my PC or other similar business). Fortunately up to
 now I have never asked for charity dear David and I hope to have not to do
 it in the future.

 Have a good dinner!

 Fernando


 On Sat, Aug 6, 2011 at 5:35 PM, David Johnston pol...@yahoo.com wrote:

 Since this thread is already top-post...

 One of the reasons software can be free is because people are able to
 make money doing things like hosting and consulting.

 If you are looking for charity because you are poor, or what you want to
 do has little commercial value, you would be wise to propose what it is you
 want to actually accomplish and the specific resources you likely need.
  Showing effort on your part will project professionalism as opposed to the
 free-loader personality that you show when you simply ask for free stuff.
  Simply pointing out that you need to eat as the reason why you need free
 hosting makes you look foolish.  The fact that you cross-posted projects
 disrespect for the very communities providing the free stuff you want to
 use.

 I'm sorry your research GRANT expired but you should focus on either
 obtaining a new grant or how to earn a regular 

Re: [GENERAL] PostgreSQL hanging on new connections?

2010-11-30 Thread Dusan Misic
On Tue, Nov 30, 2010 at 10:20 AM, Craig Ringer
cr...@postnewspapers.com.auwrote:

 On 11/30/2010 03:28 PM, Dusan Misic wrote:

We're having similar issues on 8.4.[245]... occasionally psql takes
anywhere from a few to several dozen seconds to connect. I've been
unsuccessfully trying to blame spikes in the OS run queue (we
desperately need some connection pooling) but if it's something to
do with locks I can't see in pg_locks, that would explain why I
haven't been able to figure out what's going on yet
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org
mailto:pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


 This is normal. PostgreSQL needs to create new server process to handle
 your requested connection.

 Then it needs to allocate resources to that new connection. It
 initializes shared memory for that connection. That is the stall you are
 mentioning.


 Eh, what?

 Forking a backend and attaching to shared memory should *not* take a few
 seconds. On my test machine it takes 100ms to fork psql, connect to the
 postmaster, fork a backend, init the backend, authenticate, run a dummy
 query and exit psql.

 If you're seeing delays like that, your machine is horrifyingly overloaded
 or there's something else wrong.

 --
 Craig Ringer


This is not happening to me. Even on my home computer (which is terribly
slow single core Sempron 2600+ with 128 kB of L2 cache, 1.5 GB DDR RAM and
with slow ATA hard disks) it is fast to connect. Maximum (slowest)
connection time is about 500 ms. I did some tuning in postgresql.conf.

I'm very happy with PostgreSQL speed on my 'snail' computer. :)


Re: [GENERAL] PostgreSQL hanging on new connections?

2010-11-29 Thread Dusan Misic
On Mon, Nov 29, 2010 at 10:03 PM, Ben Chobot be...@silentmedia.com wrote:

 On Nov 29, 2010, at 12:57 PM, Vick Khera wrote:

  On Mon, Nov 29, 2010 at 1:23 PM, Tom Lane t...@sss.pgh.pa.us wrote:
  hubert depesz lubaczewski dep...@depesz.com writes:
  straced postmaster when the problem was happening, and I was opening
 new
  connections. strace looks like this:
  [ backend hangs on semop immediately after reading global/pg_database ]
 
  It looks like something had exclusive lock on the database that new
  connections wanted to connect to.  AFAICS the only action in 8.3 that
  would do that would be a DROP DATABASE or RENAME DATABASE.  What was
  that other session doing?
 
  Every once in a while when I connect to my big DB it feels like it
  stalls the connection for a few seconds.  I have no idea what causes
  it, but it does feel like it has to do with the load.  The load is not
  all that high relative to what my box can handle.  It doesn't happen
  often enough for me to track it down, though.  It instinct is that it
  is waiting on a lock, but clearly there is no rename/drop happening on
  my main db else i'd be out of business :-)  I too run 8.3 as primary
  right now... testing 9.0 for deployment soon-ish.

 We're having similar issues on 8.4.[245]... occasionally psql takes
 anywhere from a few to several dozen seconds to connect. I've been
 unsuccessfully trying to blame spikes in the OS run queue (we desperately
 need some connection pooling) but if it's something to do with locks I can't
 see in pg_locks, that would explain why I haven't been able to figure out
 what's going on yet
 --
 Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
 To make changes to your subscription:
 http://www.postgresql.org/mailpref/pgsql-general


This is normal. PostgreSQL needs to create new server process to handle your
requested connection.

Then it needs to allocate resources to that new connection. It initializes
shared memory for that connection. That is the stall you are mentioning.

If you are time sensitive on connection times, then use connection pooling
software like pg-bouncer or pg-pool2. Pooling will keep your server instance
hot and those lags won't happen.