Npgsql is the .NET data provider for Postgresql. It allows any program developed for .NET framework to access a Postgresql database server. It is implemented in 100% C# code. Postgresql versions since 9.0 are officially supported, others may work.
Hi @roji - so we did not upgrade the driver recently, believe our pool hit the default max of 100 pooled connections due to load (so not ab-normal per say maybe) however the pool related bugs being worked on in 4.0.9 - npgsql/npgsql#2224 and npgsql/npgsql#2513, wondering if this could be causing our pools to grow to 100 sooner then they need (if that made sense)?
#2224 wouldn't cause your pool to grow - it would cause it not shrink - this may seem a bit subtle but it's important. It just means that in periods of inactivity the pool won't be pruned effectively, and will continue hogging physical connections which should be closed. #2513 is about abnormally high CPU usage when the pool is saturated, which again shouldn't lead to actual connection timeouts. So I wouldn't necessarily look there for an explanation why you're timing out...
@say25 the PR seems to need rebasing, aside from that I promise to review as soon as I can (times are busy...)
Hi folks was wondering if anyone has run into the following error when compiling on .Net 4.7.2 with NpgSql v4.0.8 : error CS0103: The name 'NpgsqlFactory' does not exist in the current context
I copied the example verbatim located here: https://www.npgsql.org/ef6/index.html and this has been working without error for months. I updgrade NpgSql from 4.0.7 to 4.0.8 and it is now blowing up.
Anybody know why?
When I connect to pg11 with npgsql 3.1.1 to run query bellow. Occasionally I got exception of 'System.Text.DecoderFallbackException: Unable to translate bytes [C0] at index -1 from specified code page to Unicode. at System.Text.DecoderExceptionFallbackBuffer.Throw(Byte[] bytesUnknown, Int32 index)". Query: "SELECT datname, pid, usesysid, application_name, backend_start, xact_start, query_start, state_change,wait_event_type, wait_event, state, backend_xid, backend_xmin, backend_type FROM pg_stat_activity;"
Does anyone aware of this issue?
@YunLi1988 That's odd... This kind of error would occur because of some decoding issue. That particular query (pg_stat_activity) shows what queries are currently executing, so is it possible you have queries which in their SQL have some non-standard characters? More importantly, what encoding is your database in (SHOW server_encoding) and are you setting client_encoding (in the connection string or manually)?
@AlbertoPa if you're referring to general EF Core features in 3.0.0, see https://docs.microsoft.com/en-us/ef/core/what-is-new/ef-core-3.0/features. For PostgreSQL-specific stuff, there's no page yet or anything, look at the closed issues mainly: https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.0.0
I was trying to figure out if there is a plan to support multidimensional types (either arrays or Dictionary) :-)
@AlbertoPa the issue tracking multi-dimensional arrays in EF Core is npgsql/Npgsql.EntityFrameworkCore.PostgreSQL#314
Depending on exactly what you want to do, stuff may work. If it's just about mapping properties, it should be there.
I am playing with EF core in the 3.0 preview, and I see issues with "owned" entities. How is one supposed to have them retrieved? It used to be automatic but currently I can't get the values back, even if I explicitly use Include in the EF core query...
I am playing with EF core in the 3.0 preview, and I see issues with "owned" entities. How is one supposed to have them retrieved? It used to be automatic but currently I can't get the values back, even if I explicitly use Include in the EF core query...
This is fixed now in p8. I have just tested :-)
@HohPanat_twitter you'll have to provide a bit more details.
Using the second way you need to provide multiple parameters, one for each column you're going to insert. The query will be like
INSERT INTO my_table (my_col_1, my_col_2) SELECT * FROM unnest(@myValues1, @myValues2) AS r (my_value_1, my_value_2).
In SQL Server the same thing can be achieved via SqlDataRecord collection passed to the server via a single parameter.
I've started playing with Blazor recently and adapted my side project to use server-side Blazor. I may don't understand something, but I have a function (in injected service in component) which accesses the database (Postgres via the EF Core NPGSQL driver) and returns some data. This function and another, from another service (and component), uses a common feature "GetUserAsync()" which is a standard function of UserManager. If I use both components on the same page I'm getting an error: NpgsqlOperationInProgressException: A command is already in progress: (and here is the SQL query for fetching user data). Does anyone have experience with Blazor and NGPSQL? Every package (Blazor, NPGSQL etc. in the latest preview8 version).
the recommended way (at least informally, because guidance should come later) is to inject the service as transient (not scoped, as in MVC)
AlbertoPa @AlbertoPa is very happy of EF with Postgres in p8 :tada:
Ok, it seems that I forgot to register the whole Identity as transient. After I've registered the whole bunch of services from Identity as transient it's working now - I mean no more exceptions about already running query. Thank you for your help. It's time to consider decoupling Blazor and access data via separate API because I would not say I like the idea to use every database-related service with transient lifetime scope.