Hi ,
I want to insert multiple Rows in one shot to improve my performance .
>From C# code I am using ADO .net to connect to postgres .
Currently i am pasting the code which is not of postgres but in my dev
environment similar things i am doing with Postgres.
MySqlConnection mySql = new MySqlCon
On Fri, 2 Oct 2009, Justin Pryzby wrote:
When we upgraded from linux-2.6.24 to linux-2.6.27, our pg_dump
duration increased by 20% from 5 hours to 6.
Why 2.6.27 of all versions? It's one of the versions I skipped altogether
as looking like a mess, after CFS broke everything in 2.6.23 I went
Craig James wrote:
Kevin Grittner wrote:
Which leaves the issue open -- a flexible way to flag the *reason* (or
*reasons*) for the absence of a value could be a nice enhancement, if
someone could invent a good implementation. Of course, one could
always add a column to indicate the reason for a
Kevin Grittner wrote:
Which leaves the issue open -- a flexible way to flag the *reason* (or
*reasons*) for the absence of a value could be a nice enhancement, if
someone could invent a good implementation. Of course, one could
always add a column to indicate the reason for a NULL; and perhaps
t
Guy Rouillier wrote:
> Kevin Grittner wrote:
>> A failing of the SQL standard is that it uses the same mark (NULL)
>> to show the absence of a value because it is unknown as for the
>> case where it is known that no value exists (not applicable). Codd
>> argued for a distinction there, but it
Kevin Grittner wrote:
Grzegorz Jaœkiewicz wrote:
A failing of the SQL standard is that it uses the same mark (NULL) to
show the absence of a value because it is unknown as for the case
where it is known that no value exists (not applicable). Codd argued
for a distinction there, but it hasn't
Grzegorz Jaœkiewicz wrote:
> Guy Rouillier wrote:
>> Grzegorz Jaœkiewicz wrote:
>>> using nulls as default 'idunno' - is a bad practice
>> I don't understand this point of view. The concept of null was
>> introduced into the SQL vernacular by Codd and Date expressly to
>> represent unknown val
On Mon, Oct 5, 2009 at 8:35 PM, Guy Rouillier wrote:
> Grzegorz Jaśkiewicz wrote:
>
>>
>> well, as a rule of thumb - unless you can't think of a default value of
>> column - don't use nulls. So using nulls as default 'idunno' - is a bad
>> practice, but everybody's opinion on that differ.
>>
>
> I
> -Original Message-
> >
> > The problem is, this next year we're anticipating significant growth,
> > where we may be adding more like 20 million rows per month (roughly
> 15GB
> > of data).
> >
> > A row of data might have:
> > The system identifier (int)
> > Date/Time read (timestamp)
