On 10 January 2012 15:46, Jerry Sievers wrote:
>> We're trying to migrate the app from mysql to pg and this is one of
>> the performance bottle-necks. Unfortunately it slows down every
>> request by about 5 seconds.
That's a delay that could be due to DNS problems or other network
issues. It may
Andy Chambers writes:
> Hi,
>
> I have an update that takes longer than expected and wondered if
> there's an easy way to make it go faster.
>
> It's pretty simple:-
>
> create table session (
> id serial primary key,
> data text);
>
> update session
> set data = 'ipsum lorem...'
> where
On Mon, Jan 9, 2012 at 4:30 PM, Tom Lane wrote:
Sorry. Forgot to hit "Reply to All"
Aha. I think I'd gotten carried away with some of the settings in
order to optimize for bulk loading. Reverting back to the default
postgresql.conf gets me back to the sort of times you guys are seeing
here.
On 01/09/12 1:03 PM, Andy Chambers wrote:
I have an update that takes longer than expected and wondered if
there's an easy way to make it go faster.
It's pretty simple:-
create table session (
id serial primary key,
data text);
update session
set data = 'ipsum lorem...'
where id =
Andy Chambers writes:
> I have an update that takes longer than expected and wondered if
> there's an easy way to make it go faster.
> It's pretty simple:-
> create table session (
> id serial primary key,
> data text);
> update session
> set data = 'ipsum lorem...'
> where id = 5;
> T
In response to Andy Chambers :
>
> I have an update that takes longer than expected and wondered if
> there's an easy way to make it go faster.
>
> It's pretty simple:-
>
> create table session (
> id serial primary key,
> data text);
>
> update session
> set data = 'ipsum lorem...'
> w
Hi,
I have an update that takes longer than expected and wondered if
there's an easy way to make it go faster.
It's pretty simple:-
create table session (
id serial primary key,
data text);
update session
set data = 'ipsum lorem...'
where id = 5;
The "ipsum lorem.." stuff is an encrypt
