[B! PostgreSQL] yyamanoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯

yyamano id:yyamano

PostgreSQLã«é–¢ã™ã‚‹yyamanoã®ãƒ–ãƒƒã‚¯ãƒžãƒ¼ã‚¯ (19)

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

${{author_name}}$
{{author_name}}{{created}}
{{ #comment }}{{ comment }}{{ /comment }}
- {{ label }}

${{author_name}}$

{{{comment_expanded}}}

{{label}}

{{#is_bookmark}}ãƒªã‚¹ãƒˆ{{/is_bookmark}}{{^is_bookmark}}ãƒªãƒ³ã‚¯{{/is_bookmark}}

HAProxyã§PostgreSQLã‚’è² è·åˆ†æ•£ã™ã‚‹ï¼ˆãƒ‡ãƒ¢å‹•ç”»ã‚ã‚Šï¼‰
PostgreSQLã«ãƒ¬ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³æ©Ÿèƒ½ãŒæ¨™æº–æ©Ÿèƒ½ã¨ã—ã¦å…¥ã£ã¦ã—ã°ã‚‰ãçµŒã¡ã¾ã—ãŸã€‚ PostgreSQLã§ã‚‚ãƒ¬ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³æ©Ÿèƒ½ãŒã„ã‚ã„ã‚ãªã¨ã“ã‚ã§ä½¿ã‚ã‚Œã‚‹ã‚ˆã†ã«ãªã£ã¦ããŸæœ€è¿‘ã§ã™ãŒã€ä»¥å‰ã‹ã‚‰æ°—ã«ãªã£ã¦ã„ãŸã“ã¨ã¨ã—ã¦ã€ã€ŒL4ã®ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µã§PostgreSQLã®è² è·åˆ†æ•£ãŒã§ããªã„ã®ã ã‚ã†ã‹ï¼Ÿã€ã¨ã„ã†ç´ æœ´ãªç–‘å•ãŒã‚ã‚Šã¾ã—ãŸã€‚ ãšã£ã¨è©¦ã—ã¦ã¿ãŸã„ã¨æ€ã£ã¦ã„ãŸã®ã§ã™ãŒã€ã‚ˆã†ã‚„ãä»Šå›ž HAProxy ã‚’ç”¨ã„ã‚‹ã“ã¨ã§å‹•ä½œã•ã›ã‚‹ã“ã¨ãŒã§ãã¾ã—ãŸã®ã§ã€ãã®æ–¹æ³•ã‚’ç°¡å˜ã«ã”ç´¹ä»‹ã—ã¾ã™ã€‚ â– ã€ŒL4ã®ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µã€ã¨ã¯ ã€ŒL4ï¼ˆLayer4ï¼‰ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚¹ã€ã¨ã¯TCPå±¤ã«ãŠã‘ã‚‹ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚¹ã®ã“ã¨ã§ã™ã€‚L4ã®ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µã¯ã€ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã”ã¨ã®ã‚»ãƒƒã‚·ãƒ§ãƒ³ã®å†…å®¹ã«ã¯é–¢ä¿‚ãªãã€TCPå±¤ã®æƒ…å ±ã ã‘ã‚’ä½¿ã£ã¦ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚¹ã‚’è¡Œã„ã¾ã™ã€‚ ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ã®ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚¹ã«ã¯ã€L4ä»¥å¤–ã«ã‚‚L7ã®ãƒãƒ¼ãƒ‰ãƒãƒ¼ãƒ‰ãƒãƒ©ãƒ³ã‚µã‚‚ã‚
yyamano 2015/02/28
PostgreSQL

HAProxy
ãƒªãƒ³ã‚¯
NTTãƒ‡ãƒ¼ã‚¿ã¨PostgreSQLãŒæŒ‘ã‚“ã ç·åŠ›æˆ¦ã€‚PostgreSQLã‚’æ¥µé™ã¾ã§ä½¿ã„åˆ‡ã£ãŸãã®å…ˆã«è¦‹ãŸã‚‚ã®ã¨ã¯ï¼Ÿï¼ˆå¾Œç·¨ï¼‰ NTTãƒ‡ãƒ¼ã‚¿ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹DAY2015 ï¼ Publickey
NTTãƒ‡ãƒ¼ã‚¿ã¨PostgreSQLãŒæŒ‘ã‚“ã ç·åŠ›æˆ¦ã€‚PostgreSQLã‚’æ¥µé™ã¾ã§ä½¿ã„åˆ‡ã£ãŸãã®å…ˆã«è¦‹ãŸã‚‚ã®ã¨ã¯ï¼Ÿï¼ˆå¾Œç·¨ï¼‰ NTTãƒ‡ãƒ¼ã‚¿ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹DAY2015 PostgreSQLã‚’å¤§è¦æ¨¡ãªãƒŸãƒƒã‚·ãƒ§ãƒ³ã‚¯ãƒªãƒ†ã‚£ã‚«ãƒ«ãªã‚·ã‚¹ãƒ†ãƒ ã®ä¸ã§ä½¿ã†ã«ã¯ã€ã©ã®ã‚ˆã†ãªãƒŽã‚¦ãƒã‚¦ãŒæ±‚ã‚ã‚‰ã‚Œã‚‹ã®ã‹ã€‚ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ã®åˆ©ç”¨ã«ç©æ¥µçš„ãªNTTãƒ‡ãƒ¼ã‚¿ãŒãã®äº‹ä¾‹ã‚’ã€1æœˆ26æ—¥ã«é–‹å‚¬ã•ã‚ŒãŸã‚¤ãƒ™ãƒ³ãƒˆã€ŒNTTãƒ‡ãƒ¼ã‚¿ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹DAY 2015ã€ã§ç´¹ä»‹ã—ã¦ã„ã¾ã™ã€‚è¬›æ¼”å†…å®¹ã‚’ãƒ€ã‚¤ã‚¸ã‚§ã‚¹ãƒˆã«ã—ã¾ã—ãŸã€‚ ï¼ˆæœ¬è¨˜äº‹ã¯ã€ŒNTTãƒ‡ãƒ¼ã‚¿ã¨PostgreSQLãŒæŒ‘ã‚“ã ç·åŠ›æˆ¦ã€‚PostgreSQLã‚’æ¥µé™ã¾ã§ä½¿ã„åˆ‡ã£ãŸãã®å…ˆã«è¦‹ãŸã‚‚ã®ã¨ã¯ï¼Ÿï¼ˆå‰ç·¨ï¼‰ã€ã®ç¶šãã§ã™ï¼‰ å®Ÿè¡Œè¨ˆç”»ã‚’ãƒã‚§ãƒƒã‚¯ã™ã‚‹ãŸã‚ã«PostgreSQLã‚’é¨™ã™ã€‚ 3ã¤ç›®ã¯å®Ÿè¡Œè¨ˆç”»ã®ãƒã‚§ãƒƒã‚¯ã§ã™ã€‚PostgreSQLã®SQLæ–‡ã¯ã‚³ã‚¹ãƒˆãƒ™ãƒ¼ã‚¹ã§å®Ÿè¡Œã•ã‚Œã¾ã™ã®ã§ã€çµ±è¨ˆæƒ…å ±ã‚’è¦‹ã¦ã€ãƒ†ãƒ¼ãƒ–ãƒ«ã‚’ã‚¹ã‚ãƒ£ãƒ³
yyamano 2015/02/09
PostgreSQL
ãƒªãƒ³ã‚¯
NTTãƒ‡ãƒ¼ã‚¿ã¨PostgreSQLãŒæŒ‘ã‚“ã ç·åŠ›æˆ¦ã€‚PostgreSQLã‚’æ¥µé™ã¾ã§ä½¿ã„åˆ‡ã£ãŸãã®å…ˆã«è¦‹ãŸã‚‚ã®ã¨ã¯ï¼Ÿï¼ˆå‰ç·¨ï¼‰ NTTãƒ‡ãƒ¼ã‚¿ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹DAY2015 ï¼ Publickey
NTTãƒ‡ãƒ¼ã‚¿ã¨PostgreSQLãŒæŒ‘ã‚“ã ç·åŠ›æˆ¦ã€‚PostgreSQLã‚’æ¥µé™ã¾ã§ä½¿ã„åˆ‡ã£ãŸãã®å…ˆã«è¦‹ãŸã‚‚ã®ã¨ã¯ï¼Ÿï¼ˆå‰ç·¨ï¼‰ NTTãƒ‡ãƒ¼ã‚¿ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹DAY2015 ç¾åœ¨ã®ã‚·ã‚¹ãƒ†ãƒ æ§‹ç¯‰ã§ã¯ã€ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ã®ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢ã‚’ä½¿ã†ã“ã¨ã¯å½“ãŸã‚Šå‰ã«ãªã£ã¦ãã¦ã„ã¾ã™ã€‚PostgreSQLã¯ãã†ã—ãŸä¸ã§ä¸»ã«ã‚¨ãƒ³ã‚¿ãƒ¼ãƒ—ãƒ©ã‚¤ã‚ºå‘ã‘ã®ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã¨ã—ã¦ç€å®Ÿã«äº‹ä¾‹ã‚’å¢—ã‚„ã—ã¦ãã¦ã„ã¾ã™ã€‚ ãã®ä¸ã§ã€PostgreSQLã‚’å¤§è¦æ¨¡ãªãƒŸãƒƒã‚·ãƒ§ãƒ³ã‚¯ãƒªãƒ†ã‚£ã‚«ãƒ«ãªã‚·ã‚¹ãƒ†ãƒ ã®ä¸ã§ä½¿ã†ã«ã¯ã€ã©ã®ã‚ˆã†ãªãƒŽã‚¦ãƒã‚¦ãŒæ±‚ã‚ã‚‰ã‚Œã‚‹ã®ã‹ã€‚ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ã®åˆ©ç”¨ã«ç©æ¥µçš„ãªNTTãƒ‡ãƒ¼ã‚¿ãŒãã®äº‹ä¾‹ã‚’ã€1æœˆ26æ—¥ã«é–‹å‚¬ã•ã‚ŒãŸã‚¤ãƒ™ãƒ³ãƒˆã€ŒNTTãƒ‡ãƒ¼ã‚¿ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹DAY 2015ã€ã®ã‚»ãƒƒã‚·ãƒ§ãƒ³ã€ŒNTTãƒ‡ãƒ¼ã‚¿ã¨PostgreSQLãŒæŒ‘ã‚“ã ç·åŠ›æˆ¦ã€‚PostgreSQLã‚’æ¥µé™ã¾ã§ä½¿ã„åˆ‡ã£ãŸãã®å…ˆã«è¦‹ãŸã‚‚ã®ã¨ã¯ï¼Ÿã€ã§ç´¹ä»‹ã—ã¦ã„ã¾ã™ã€‚è¬›æ¼”å†…å®¹ã‚’ãƒ€ã‚¤ã‚¸ã‚§ã‚¹ãƒˆã«ã—ã¾ã—
yyamano 2015/02/09
PostgreSQL
ãƒªãƒ³ã‚¯
9.4 performance improvements test
yyamano 2014/10/20
â€œI suspect this is due to the improvements in writing less to WAL. If so, good work, guys!â€

PostgreSQL
ãƒªãƒ³ã‚¯
28.3.Â Write-Ahead Logging (WAL)
Write-Ahead Logging (WAL) is a standard method for ensuring data integrity. A detailed description can be found in most (if not all) books about transaction processing. Briefly, WAL's central concept is that changes to data files (where tables and indexes reside) must be written only after those changes have been logged, that is, after WAL records describing the changes have been flushed to perman
yyamano 2014/10/20
â€œWAL's central concept is that changes to data files (where tables and indexes reside) must be written only after those changes have been logged, that is, after log records describing the changes have been flushed to permanent storage. â€

PostgreSQL
ãƒªãƒ³ã‚¯
Tatsuo Ishii on Twitter: "PGCon2014 PostgreSQLã®JSONBåž‹ã¨MongoDBã®æ€§èƒ½æ¯”è¼ƒã€‚120ä¸‡ä»¶ã®jsonãƒ‡ãƒ¼ã‚¿ã®ãƒãƒ¼ãƒ‰ã«JSONBãŒ43ç§’ãªã®ã«å¯¾ã—ã€MongoDBã¯13åˆ†ã€æ¤œç´¢ã¯JSONBãŒ0.7msã€MongoDBã¯1msã€‚"
yyamano 2014/05/23
â€œ20ä¸‡ä»¶ã®jsonãƒ‡ãƒ¼ã‚¿ã®ãƒãƒ¼ãƒ‰ã«JSONBãŒ43ç§’ãªã®ã«å¯¾ã—ã€MongoDBã¯13åˆ†ã€æ¤œç´¢ã¯JSONBãŒ0.7msã€MongoDBã¯1msã€‚ â€

MongoDB

PostgreSQL
ãƒªãƒ³ã‚¯
PostgreSQLã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£å…¥é–€ï¼ˆINSIGHT OUT 2011ï¼‰
2011å¹´10æœˆ19ï½ž21æ—¥ã«é–‹å‚¬ã•ã‚ŒãŸã€ŒINSIGHT OUT 2011ã€ã®ã‚»ãƒƒã‚·ãƒ§ãƒ³ã€ŒPostgreSQLã‚¢ãƒ¼ã‚ãƒ†ã‚¯ãƒãƒ£å…¥é–€ã€ã®è¬›æ¼”è³‡æ–™ã§ã™ã€‚ ã€ŒINSIGHT OUT 2011ã€ã®è©³ç´°ã«ã¤ã„ã¦ã¯ã€ä»¥ä¸‹ã‚’å‚ç…§ãã ã•ã„ã€‚ http://www.insight-tec.com/insight-out-2011.htmlRead less
yyamano 2013/12/15
PostgreSQL
ãƒªãƒ³ã‚¯
Apache JMeterã§PostgreSQLã®è² è·è©¦é¨“ã‚’ã™ã‚‹
ã“ã®ã‚¨ãƒ³ãƒˆãƒªã¯ã€PostgreSQL Advent Calendar 2013ã®Day3ã®è¨˜äº‹ã§ã™ã€‚ ã€Œãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã®è² è·è©¦é¨“ã€ã‚’è€ƒãˆã‚‹æ™‚ã€çš†ã•ã‚“ã¯ã©ã®ã‚ˆã†ãªæ–¹æ³•ã§å®Ÿæ–½ã™ã‚‹ã“ã¨ã‚’æ¤œè¨Žã™ã‚‹ã§ã—ã‚‡ã†ã‹ã€‚è‡ªå‰ã®ãƒ†ã‚¹ãƒˆã‚¹ã‚¯ãƒªãƒ—ãƒˆã§ã—ã‚‡ã†ã‹ã€‚ã‚ã‚‹ã„ã¯ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹å˜ä½“ã®è² è·è©¦é¨“ã¯è¡Œã‚ãšã€Webã‚·ã‚¹ãƒ†ãƒ å…¨ä½“ã®è² è·è©¦é¨“ã¨ã—ã¦å®Ÿæ–½ã™ã‚‹ã§ã—ã‚‡ã†ã‹ã€‚ PostgreSQLã«ã¯ã€pgbenchã¨ã„ã†ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ãƒ„ãƒ¼ãƒ«ãŒä»˜å±žã—ã¦ãŠã‚Šã€ã“ã®ãƒ„ãƒ¼ãƒ«ã®ã‚·ãƒŠãƒªã‚ªã‚’ä½œæˆã™ã‚‹ã“ã¨ã§å¤šå°‘ã¯ç‹¬è‡ªã®ã‚·ãƒŠãƒªã‚ªã§ã®è©¦é¨“ã‚’è¡Œã†ã“ã¨ã‚‚å¯èƒ½ã§ã™ãŒã€çŠ¶æ³ã«ã‚ˆã£ã¦ã¯ãã‚Œã ã‘ã§ã¯è‡ªç”±åº¦ãŒä¸è¶³ã™ã‚‹ã“ã¨ãŒã‚ã‚Šã¾ã™ã€‚ ä»Šå›žã¯ã€Webã‚·ã‚¹ãƒ†ãƒ ã®è² è·ãƒ†ã‚¹ãƒˆã§ã‚ˆãä½¿ã‚ã‚Œã‚‹JMeterã‚’ä½¿ã£ã¦ã€è‡ªç”±ãªã‚·ãƒŠãƒªã‚ªã§PostgreSQLå˜ä½“ã®è² è·è©¦é¨“ã‚’è¡Œã†æ–¹æ³•ã‚’ç´¹ä»‹ã—ã¾ã™ã€‚ ï¼ˆãªãŠã€JMeterã¯éžå¸¸ã«å¤šæ©Ÿèƒ½ãªè² è·ç”Ÿæˆãƒ„ãƒ¼ãƒ«ã§ã™ã®ã§ã€ä»Šå›žã¯JMeterã®ç¶²ç¾…çš„ãªèª¬æ˜Ž
yyamano 2013/12/03
PostgreSQL

Performance
ãƒªãƒ³ã‚¯
PostgreSQL: Don't Use CHAR or VARCHAR
tl;dr: Use TEXT instead of VARCHAR or CHAR; TEXT has exactly the same performance and space usage characteristics while being much more flexible. Earlier this week, while browsing some stack overflow questions about postgres' textual data types, I came across a link to a set of benchmarks that compare the performance of the CHAR, VARCHAR, and TEXT types in PostgreSQL â€” I highly recommend reading t
yyamano 2013/11/22
PostgreSQL
ãƒªãƒ³ã‚¯
RDS for PostgreSQLã®ä¸ã‚’è¦—ã„ã¦ã¿ãŸï¼ˆè¿½è¨˜ã‚ã‚Šï¼‰
çš†ã•ã‚“ãŠå¾…ã¡ã‹ãã®ã€RDS for PostgreSQLãŒæ˜¨æ—¥ãƒªãƒªãƒ¼ã‚¹ã•ã‚Œã¾ã—ãŸã€‚ Amazon Web Services ãƒ–ãƒã‚°: ã€AWSç™ºè¡¨ã€‘Amazon RDS for PostgreSQLãŒã”åˆ©ç”¨å¯èƒ½ã«ãªã‚Šã¾ã—ãŸï¼ http://aws.typepad.com/aws_japan/2013/11/amazon-rds-for-postgresql-now-available.html æ—¢ã«ã‚¤ãƒ³ã‚¹ã‚¿ãƒ³ã‚¹ã‚’ç«‹ã¡ä¸Šã’ã¦ã¿ãŸæ–¹ã‚‚ã„ã‚‹ã‚ˆã†ã§ã™ã€‚ Amazon RDS for PostgreSQLãŒã‚„ã£ã¦ããŸï¼ï¼ ï½œ Developers.IO http://dev.classmethod.jp/cloud/amazon-rds-for-postgresql-now-on-sale/ cloudpackãƒ–ãƒã‚°: Amazon RDS ã§ PostgreSQL ãŒåˆ©ç”¨å¯èƒ½ã« http://bl
yyamano 2013/11/18
PostgreSQL

Amazon
ãƒªãƒ³ã‚¯
MySQL ã§ã¯ GROUP BY å¥ã‚’ä½¿ç”¨ã—ãŸå ´åˆã§ã‚‚é›†ç´„ã•ã‚Œã¦ã„ãªã„åˆ—ã‚’çµæžœã«å«ã‚ã‚‹ã“ã¨ãŒã§ãã‚‹ - ã²ã ã¾ã‚Šã‚½ã‚±ãƒƒãƒˆã¯å£Šã‚Œãªã„
è¡¨é¡Œã©ãŠã‚Šã€‚ æ™®é€šã€SQL ã§ GROUP BY å¥ã‚’ä½¿ç”¨ã—ã¦ SELECT ã™ã‚‹å ´åˆã€çµæžœã«å«ã‚ã‚‹ã“ã¨ãŒã§ãã‚‹åˆ—ã¯ GROUP BY å¥ã«å«ã¾ã‚Œã‚‹åˆ—ã‹é›†ç´„é–¢æ•° (aggregate functions) ã‚’é©ç”¨ã—ãŸåˆ—ã®ã¿ã§ã™ã€‚ ã—ã‹ã—ã€MySQL ã®å ´åˆã¯ãã†ã§ã¯ãªãã€GROUP BY å¥ã«ã‚‚å«ã¾ã‚Œã¦ã„ãªã„ã—é›†ç´„é–¢æ•°ã‚‚é€šã—ã¦ã„ãªã„åˆ—ã‚’çµæžœã«å«ã‚ã‚‹ã“ã¨ãŒã§ãã¾ã™ã€‚ ä»•äº‹ã§è§¦ã£ã¦ã‚‹ãƒ—ãƒã‚°ãƒ©ãƒ ã®ä¸ã«ãã†ã„ã†ã‚¯ã‚¨ãƒªã‚’ç™ºè¡Œã™ã‚‹ SQL ãŒã‚ã£ã¦ ã€Œãƒžã‚¸ã‹!!ã€ ã£ã¦æ€ã£ãŸã®ã§ã™ãŒã€èª¿ã¹ã¦ã¿ã‚‹ã¨ãƒ‘ãƒ•ã‚©ãƒ¼ãƒžãƒ³ã‚¹ã®ãŸã‚ã«ãã†ã„ã†æ‹¡å¼µãŒãªã•ã‚Œã¦ã„ã‚‹ã¨ã®ã“ã¨ã§ã—ãŸã€‚ MySQL extends the use of GROUP BY so that the select list can refer to nonaggregated columns not named in the GROUP BY cla
yyamano 2013/10/24
PostgreSQL
ãƒªãƒ³ã‚¯
Upfront Software
UPFRONT SOFTWARE We create custom software that will rock your world. find out more About us Upfront Software was founded in 1997. We create custom software for all modern web browsers and develop native mobile apps for iOS and Android devices. We build software that makes it easier for individuals and businesses to use and handle large volumes of information. We use familiar user interfaces and p
yyamano 2013/10/24
PostgreSQL
ãƒªãƒ³ã‚¯
CREATE ROLE
yyamano 2013/10/24
PostgreSQL
ãƒªãƒ³ã‚¯
ä¼æ¥ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã¨ã—ã¦PostgreSQLãŒMySQLã‚ˆã‚Šå„ªã‚Œã¦ã„ã‚‹ã‚ã‘ - builder by ZDNet Japan
ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã¨ã—ã¦ã¯ã€MySQLãŒåœ§å€’çš„ãªæ³¨ç›®ã‚’é›†ã‚ã¦ã„ã‚‹ã€‚MySQLã¯ä½¿ã„ã‚„ã™ã„ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã§ã‚ã‚Šã€å¤šãã®ã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ã‚¦ã‚§ãƒ–ã‚¢ãƒ—ãƒªã‚±ãƒ¼ã‚·ãƒ§ãƒ³ã¯MySQLã‚’ä½¿ã£ã¦ã„ã‚‹ã€‚åˆ¥ã®ä¸»è¦ãªã‚ªãƒ¼ãƒ—ãƒ³ã‚½ãƒ¼ã‚¹ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã¨ã—ã¦PostgreSQLãŒã‚ã‚Šã€åºƒãçŸ¥ã‚‰ã‚Œã¦ã¯ã„ã‚‹ãŒã€MySQLã»ã©ã®ãƒžã‚¤ãƒ³ãƒ‰ã‚·ã‚§ã‚¢ã¯ãªã„ã€‚PostgreSQLãŒMySQLã‚ˆã‚Šã‚‚ã€ã‚ˆã‚Šã‚ˆã„ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ã€ä¿¡é ¼æ€§ã€ãƒ‡ãƒ¼ã‚¿ã®å®Œå…¨æ€§ã‚’æä¾›ã—ã¦ã„ã‚‹ã“ã¨ã‚’è€ƒãˆã‚‹ã¨ã€ã“ã‚Œã¯ä¸å¹¸ãªã“ã¨ã ã€‚ ã—ã‹ã—ã€ã“ã‚Œã‚‰ã®å„ªä½ç‚¹ã«ã¯ä»£å„ŸãŒã‚ã‚‹ã€‚PostgreSQLã¯è¨å®šã‚‚åˆ©ç”¨ã‚‚ã‚„ã‚„é›£ã—ã„ã€‚PostgreSQLã§ã¯ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹å†…ã§æä¾›ã•ã‚Œã‚‹ãƒãƒ¼ãƒ«ã¨ç‰¹æ¨©ã«åŠ ãˆã€åŸºç›¤ã¨ãªã‚‹OSã®ç‰¹æ¨©ã‚„ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ã‚’æ´»ç”¨ã—ã¦ã„ã‚‹ã€‚ã“ã®ãŸã‚ã€ã“ã‚Œã‚‰ã®å•é¡Œã«ã¤ã„ã¦çŸ¥ã‚‰ãªã„å ´åˆã€PostgreSQLã¯ä½¿ã„ã«ãããªã‚‹å ´åˆãŒã‚ã‚‹ã€‚ãŸã ã—ã“ã‚Œã‚‰ã®ã“ã¨ã‚’çŸ¥ã£ã¦ã—ã¾ãˆã°ã€PostgreS
yyamano 2013/10/23
PostgreSQLã§ã¯ã€ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹å†…ã§æä¾›ã•ã‚Œã‚‹ãƒãƒ¼ãƒ«ã¨ç‰¹æ¨©ã«åŠ ãˆã€åŸºç›¤ã¨ãªã‚‹OSã®ç‰¹æ¨©ã‚„ã‚»ã‚ãƒ¥ãƒªãƒ†ã‚£ã‚’æ´»ç”¨ã—ã¦ã„ã‚‹ã€‚ã“ã®ãŸã‚ã€ã“ã‚Œã‚‰ã®å•é¡Œã«ã¤ã„ã¦çŸ¥ã‚‰ãªã„å ´åˆã€PostgreSQLã¯ä½¿ã„ã«ãããªã‚‹å ´åˆãŒã‚ã‚‹ã€‚

PostgreSQL
ãƒªãƒ³ã‚¯
é•·å¹´ã®è°è«–ã«çµ‚æ¢ç¬¦ -- MySQLã€MariaDBã€PostgreSQLã®ã‚ªãƒ—ãƒ†ã‚£ãƒžã‚¤ã‚¶/ã‚¨ã‚¯ã‚¼ã‚ãƒ¥ãƒ¼ã‚¿æ¯”è¼ƒ - interdbâ€™s blog
https://mariadb.com/kb/en/optimizer-switch/ã«ã‚ã‚‹ã‚ˆã†ã«ã€MariaDBã®ã‚ªãƒ—ãƒ†ã‚£ãƒžã‚¤ã‚¶ã¯ã‹ãªã‚Šæ”¹è‰¯ã•ã‚Œã¦ã„ã‚‹ã€‚ ã§ã¯ã€MariaDBã®ã‚ªãƒ—ãƒ†ã‚£ãƒžã‚¤ã‚¶/ã‚¨ã‚¯ã‚¼ã‚ãƒ¥ãƒ¼ã‚¿ã¯ã©ã®ç¨‹åº¦å„ªç§€ã‹ã€ï¼”ã¤ã®SELECTæ–‡ã®å®Ÿè¡Œã‚’é€šã—ã¦MySQLã¨(ã¤ã„ã§ã«PostgreSQLã¨)æ¯”è¼ƒã—ã¦ã¿ã‚‹ã€‚ (2014.12.3è¿½è¨˜ï¼šã‚ªãƒ—ãƒ†ã‚£ãƒžã‚¤ã‚¶ã«ã¤ã„ã¦ã¯çœç•¥ã—ã¦ã¾ã™ãŒã€ã“ã‚“ãªæœ¬ãŒã§ã¾ã™ã€‚) çµè«–ã‚’å…ˆã«ã„ãˆã°ã€ŒMySQLã¯æ¤œç´¢ãŒé€Ÿã„ã€ã¨ã„ã†ã®ã¯éƒ½å¸‚ä¼èª¬ã€‚MariaDBã¯ãŒã‚“ã°ã£ã¦ã‚‹ã‘ã©PostgreSQLã«ã¯ã¾ã ã¾ã åŠã°ãšã€‚ ï¼Šå¿µã®ãŸã‚ã€‚ã“ã‚Œã¯ãƒ™ãƒ³ãƒãƒžãƒ¼ã‚¯ã˜ã‚ƒãªã„ã‚ˆã€ã‚ªãƒ—ãƒ†ã‚£ãƒžã‚¤ã‚¶/ã‚¨ã‚¯ã‚¼ã‚ãƒ¥ãƒ¼ã‚¿ã®æ©Ÿèƒ½æ¯”è¼ƒã§ã™ã€‚ è‡ªåˆ†ã§å†ç¢ºèªã—ãŸã„å ´åˆã¯ã“ã¡ã‚‰ã«ã‚¹ã‚¯ãƒªãƒ—ãƒˆç¾¤ã¨å®Ÿé¨“ã®ã‚„ã‚Šæ–¹ã‚’ç°¡å˜ã«æ›¸ã„ãŸã®ã§å‚ç…§ã®ã“ã¨ã€‚ èª¿æŸ»ç’°å¢ƒ åŒä¸€ãƒžã‚·ãƒ³ã«MySQL5.6.14ã€MariaDB10.0.4ã€
yyamano 2013/10/23
MySQL

PostgreSQL
ãƒªãƒ³ã‚¯
PostgreSQLã®ä½¿ã„æ–¹
PostgreSQL ã¯ä¸–ç•Œä¸ã§åºƒãåˆ©ç”¨ã•ã‚Œã¦ã„ã‚‹ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã®ä¸€ã¤ã§ã™ã€‚ã“ã“ã§ã¯ PostgreSQL ã‚’ã“ã‚Œã‹ã‚‰ä½¿ã‚ã‚Œã‚‹æ–¹ã‚’å¯¾è±¡ã¨ã—ãŸ PostgreSQL å…¥é–€ã‚’æŽ²è¼‰ã—ã¾ã™ã€‚ PostgreSQL ã®ã‚¤ãƒ³ã‚¹ãƒˆãƒ¼ãƒ«æ–¹æ³•ã‚„ã€ PostgreSQL ã‚’ä½¿ã£ã¦ãƒ‡ãƒ¼ã‚¿ãƒ™ãƒ¼ã‚¹ã‚’æ§‹ç¯‰ã™ã‚‹æ‰‹é †ã«ã¤ã„ã¦ç°¡å˜ãªã‚µãƒ³ãƒ—ãƒ«ã‚’ä½¿ã£ã¦å®Ÿéš›ã«è©¦ã—ãªãŒã‚‰ä¸€ã¤ä¸€ã¤è§£èª¬ã—ã¦ã„ãã¾ã™ã€‚
yyamano 2013/10/22
PostgreSQL
ãƒªãƒ³ã‚¯
Heroku Postgres Databases Patched
Heroku Postgres Databases have been patched Data is one of the most valuable assets of any company. As a database-as-a-service provider, one of our biggest responsibilities is ensuring your data is kept safe. A few weeks ago, one of the worst security vulnerabilities to date in PostgreSQL was discovered. To address this issue, Heroku deployed a point release upgrade across the entire Heroku Postgr
yyamano 2013/04/05
Heroku

PostgreSQL

Security
ãƒªãƒ³ã‚¯
PostgreSQL: 2013-04-04 Security Release FAQ
The following versions make up this release: v9.2.4 v9.1.9 v9.0.13 v8.4.17 While this FAQ covers the 2013-04-04 PostgreSQL Security Update in general, most of its contents focus on the primary security vulnerability patched in the release, CVE-2013-1899. Are there any known exploits "in the wild" for this vulnerability? There were no known exploits at the time of release. Who is particularly vulne
yyamano 2013/04/05
PostgreSQL

Security
ãƒªãƒ³ã‚¯
Upcoming PostgreSQL Security Release: April 4, 2013
Upcoming PostgreSQL Security Release: April 4, 2013 The PostgreSQL Global Development Group will be releasing a security update for all supported versions on Thursday April 4th, 2013. This release will include a fix for a high-exposure security vulnerability. All users are strongly urged to apply the update as soon as it is available. We are providing this advance notice so that users may schedule
yyamano 2013/04/02
PostgreSQL

Security
ãƒªãƒ³ã‚¯
1