agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedThank you: an anti-question (or a Pg love letter)
3+ messages / 3 participants
[nested] [flat]
* Thank you: an anti-question (or a Pg love letter)
@ 2015-04-03 23:01 Steve Midgley <science@misuse.org>
2015-04-07 04:21 ` Re: Thank you: an anti-question (or a Pg love letter) Andrej <andrej.groups@gmail.com>
0 siblings, 1 reply; 3+ messages in thread
From: Steve Midgley @ 2015-04-03 23:01 UTC (permalink / raw)
To: pgsql-sql
Hi,
I used to participate on this list awhile back (2008?). I migrated off to
other stuff, but I'm back doing some Pg work recently. I don't have a
question, but I wanted to share my experiences, since I think the core
members of this community don't get thanked enough.
Today I had a burly (for me) problem involving transforming some text into
some json fields for ~1M rows. Running with middleware doing the schema
transforms I was getting maybe 100 rows per second. Ugh. I could go back to
the original couchdb project, but double ugh. So I re-wrote with native
Postgres SQL:
update raw_documents set
identity = json_extract_path(raw_data::json, 'identity'::text),
keys = json_extract_path(raw_data::json, 'keys'::text),
payload_schema = json_extract_path(raw_data::json, 'payload_schema'::text)
I don't even know how many rows per second b/c it came back in less than 5
minutes - maybe 3k rows per second?
I just wanted to write to say thank you to everyone who builds, supports
and participates in the Postgres community. I'm done dinking around with
different tool chains. If I have to persist something again, I'm doing it
with Postgres, I don't care if it's json, xml, cols/rows or blobs. If I
can't put save it to the filesystem, it's going in Pg. :)
Per the subject, this is an "anti-question" -- just sharing on Friday
afternoon that Postgres is working perfectly - just as it should: fast,
reliable, easy, conformant. Have a nice weekend and thank you!
Steve
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Thank you: an anti-question (or a Pg love letter)
2015-04-03 23:01 Thank you: an anti-question (or a Pg love letter) Steve Midgley <science@misuse.org>
@ 2015-04-07 04:21 ` Andrej <andrej.groups@gmail.com>
2015-04-07 14:03 ` Re: Thank you: an anti-question (or a Pg love letter) john <johnf@jfcomputer.com>
0 siblings, 1 reply; 3+ messages in thread
From: Andrej @ 2015-04-07 04:21 UTC (permalink / raw)
To: Steve Midgley <science@misuse.org>; +Cc: pgsql-sql
Thanks for sharing :)
Pure awesomeness!
On 4 April 2015 at 12:01, Steve Midgley <science@misuse.org> wrote:
> Hi,
>
> I used to participate on this list awhile back (2008?). I migrated off to
> other stuff, but I'm back doing some Pg work recently. I don't have a
> question, but I wanted to share my experiences, since I think the core
> members of this community don't get thanked enough.
>
> Today I had a burly (for me) problem involving transforming some text into
> some json fields for ~1M rows. Running with middleware doing the schema
> transforms I was getting maybe 100 rows per second. Ugh. I could go back to
> the original couchdb project, but double ugh. So I re-wrote with native
> Postgres SQL:
>
> update raw_documents set
> identity = json_extract_path(raw_data::json, 'identity'::text),
> keys = json_extract_path(raw_data::json, 'keys'::text),
> payload_schema = json_extract_path(raw_data::json, 'payload_schema'::text)
>
> I don't even know how many rows per second b/c it came back in less than 5
> minutes - maybe 3k rows per second?
>
> I just wanted to write to say thank you to everyone who builds, supports and
> participates in the Postgres community. I'm done dinking around with
> different tool chains. If I have to persist something again, I'm doing it
> with Postgres, I don't care if it's json, xml, cols/rows or blobs. If I
> can't put save it to the filesystem, it's going in Pg. :)
>
> Per the subject, this is an "anti-question" -- just sharing on Friday
> afternoon that Postgres is working perfectly - just as it should: fast,
> reliable, easy, conformant. Have a nice weekend and thank you!
>
> Steve
>
>
--
Please don't top post, and don't use HTML e-Mail :} Make your quotes concise.
http://www.georgedillon.com/web/html_email_is_evil.shtml
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Thank you: an anti-question (or a Pg love letter)
2015-04-03 23:01 Thank you: an anti-question (or a Pg love letter) Steve Midgley <science@misuse.org>
2015-04-07 04:21 ` Re: Thank you: an anti-question (or a Pg love letter) Andrej <andrej.groups@gmail.com>
@ 2015-04-07 14:03 ` john <johnf@jfcomputer.com>
0 siblings, 0 replies; 3+ messages in thread
From: john @ 2015-04-07 14:03 UTC (permalink / raw)
To: pgsql-sql
+1
Johnf
On 04/06/2015 09:21 PM, Andrej wrote:
> Thanks for sharing :)
>
> Pure awesomeness!
>
> On 4 April 2015 at 12:01, Steve Midgley <science@misuse.org> wrote:
>> Hi,
>>
>> I used to participate on this list awhile back (2008?). I migrated off to
>> other stuff, but I'm back doing some Pg work recently. I don't have a
>> question, but I wanted to share my experiences, since I think the core
>> members of this community don't get thanked enough.
>>
>> Today I had a burly (for me) problem involving transforming some text into
>> some json fields for ~1M rows. Running with middleware doing the schema
>> transforms I was getting maybe 100 rows per second. Ugh. I could go back to
>> the original couchdb project, but double ugh. So I re-wrote with native
>> Postgres SQL:
>>
>> update raw_documents set
>> identity = json_extract_path(raw_data::json, 'identity'::text),
>> keys = json_extract_path(raw_data::json, 'keys'::text),
>> payload_schema = json_extract_path(raw_data::json, 'payload_schema'::text)
>>
>> I don't even know how many rows per second b/c it came back in less than 5
>> minutes - maybe 3k rows per second?
>>
>> I just wanted to write to say thank you to everyone who builds, supports and
>> participates in the Postgres community. I'm done dinking around with
>> different tool chains. If I have to persist something again, I'm doing it
>> with Postgres, I don't care if it's json, xml, cols/rows or blobs. If I
>> can't put save it to the filesystem, it's going in Pg. :)
>>
>> Per the subject, this is an "anti-question" -- just sharing on Friday
>> afternoon that Postgres is working perfectly - just as it should: fast,
>> reliable, easy, conformant. Have a nice weekend and thank you!
>>
>> Steve
>>
>>
>
>
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2015-04-07 14:03 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2015-04-03 23:01 Thank you: an anti-question (or a Pg love letter) Steve Midgley <science@misuse.org>
2015-04-07 04:21 ` Andrej <andrej.groups@gmail.com>
2015-04-07 14:03 ` john <johnf@jfcomputer.com>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox