tag:blogger.com,1999:blog-164659665444159945.comments2023-05-18T11:30:06.606+01:00PostgreSQL DbaAnonymoushttp://www.blogger.com/profile/02966919995930930023noreply@blogger.comBlogger25125tag:blogger.com,1999:blog-164659665444159945.post-3491802248535551362017-05-25T11:13:26.282+01:002017-05-25T11:13:26.282+01:00indirectly, using bottled water
https://www.confl...indirectly, using bottled water <br />https://www.confluent.io/blog/bottled-water-real-time-integration-of-postgresql-and-kafka/The Doctorhttps://www.blogger.com/profile/18301101170664650551noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-39454215918139770152017-05-25T10:49:34.685+01:002017-05-25T10:49:34.685+01:00Hi Federico,
Can this replication be integrated w...Hi Federico,<br /><br />Can this replication be integrated with Kafka?<br /><br />Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-85654942444469960132017-01-20T00:05:49.209+00:002017-01-20T00:05:49.209+00:00good post.good post.stevenjocbhttps://www.blogger.com/profile/02803449928354344135noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-18053079246611365792017-01-19T23:54:57.340+00:002017-01-19T23:54:57.340+00:00good one.good one.stevenjocbhttps://www.blogger.com/profile/02803449928354344135noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-82911943608733759352016-12-09T09:15:41.364+00:002016-12-09T09:15:41.364+00:00I think systemd could be part of slackware if the ...I think systemd could be part of slackware if the following things are true.<br /><br />1) it becomes stable enough to be accepted by slackware. Not in the long term I'm afraid. I'm following the bugs on debian and everyday there's an issue.<br /><br />2) The developers become more collaborative and stop blaming others for their faults. Probably the Hell will froze first :PThe Doctorhttps://www.blogger.com/profile/18301101170664650551noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-19229849520718432262016-12-09T08:33:08.628+00:002016-12-09T08:33:08.628+00:00Welcome to Slackware :-)
I wondered, for a while,...Welcome to Slackware :-)<br /><br />I wondered, for a while, if Slackware might adopt systemd. Those fears were put to rest when the Slackware team worked hip-to-hip with the eudev team to migrate Slackware to eudev. The only reason to do that is to avoid the systemd dependency, and they invested a lot of time and effort in it. They wouldn't have done that if they weren't determined to keep systemd out of Slackware.TTK Ciarhttp://ciar.org/ttk/noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-43135130614655939792016-12-03T18:19:59.249+00:002016-12-03T18:19:59.249+00:00
Nice Article !
This is my pleasure to read your a...<br />Nice Article !<br />This is my pleasure to read your article.<br />Really this will help to people of PostgreSQL Community. <br /><br />I have also prepared one article about, CLUSTER command of PostgreSQL to improve the performanc of Index. <br />You can also visit my article, your comments and reviews are most welcome. <br /><br />http://www.dbrnd.com/2016/12/postgresql-cluster-improve-index-performance-no-default-cluster-index-explicit-lock-physical-order-data/Anonymoushttps://www.blogger.com/profile/01365030762397385247noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-81959877732412435912016-11-20T23:24:37.330+00:002016-11-20T23:24:37.330+00:00Thanks :)Thanks :)The Doctorhttps://www.blogger.com/profile/18301101170664650551noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-66297415702683881602016-11-20T12:16:36.320+00:002016-11-20T12:16:36.320+00:00Welcome to Slackware! And, exactly like you said, ...Welcome to Slackware! And, exactly like you said, this operating system is stable, up-to-date and simple to understand.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-62748552626003781982016-09-20T19:16:17.750+01:002016-09-20T19:16:17.750+01:00Interesting project.
Previous poster probably use...Interesting project. <br />Previous poster probably used http://flake8.pycqa.org/en/latest/ to generate those recommendations. Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-18439432387448811522016-09-20T09:26:26.484+01:002016-09-20T09:26:26.484+01:00Thanks. What did you use for the check? Thanks. What did you use for the check? The Doctorhttps://www.blogger.com/profile/18301101170664650551noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-87422965208202114882016-09-20T07:58:43.743+01:002016-09-20T07:58:43.743+01:00"I use tabs (4 space tabs)" - your ide/e..."I use tabs (4 space tabs)" - your ide/editor sucks ;)<br /><br />1 E101 indentation contains mixed spaces and tabs<br />10 E128 continuation line under-indented for visual indent<br />1 E201 whitespace after '['<br />5 E202 whitespace before ')'<br />1 E203 whitespace before ','<br />1 E211 whitespace before '('<br />1 E221 multiple spaces before operator<br />1 E222 multiple spaces after operator<br />321 E225 missing whitespace around operator<br />56 E231 missing whitespace after ','<br />4 E251 unexpected spaces around keyword / parameter equals<br />6 E265 block comment should start with '# '<br />2 E271 multiple spaces after keyword<br />4 E302 expected 2 blank lines, found 0<br />13 E303 too many blank lines (3)<br />1 E402 module level import not at top of file<br />63 E501 line too long (80 > 79 characters)<br />1 E712 comparison to True should be 'if cond is True:' or 'if cond:'<br />1100 W191 indentation contains tabs<br />109 W291 trailing whitespace<br />111 W293 blank line contains whitespace<br />1 W391 blank line at end of file<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-42955538202649906702016-09-15T20:31:25.859+01:002016-09-15T20:31:25.859+01:00Nice Article !
This is my pleasure to read your ar...Nice Article !<br />This is my pleasure to read your article.<br />Really this will help to people of PostgreSQL Community. <br /><br />I have also prepared one article about, How to create or change default tablespace in PostgreSQL. <br />You can also visit my article, your comments and reviews are most welcome. <br /><br />http://www.dbrnd.com/2016/09/postgresql-create-or-change-default-tablespace-of-table-to-migrate-on-ssd-solid-state-drive-better-performance/Anonymoushttps://www.blogger.com/profile/01365030762397385247noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-1368407149549948322016-07-01T14:57:23.825+01:002016-07-01T14:57:23.825+01:00Having a backup is only of value if the data is us...Having a backup is only of value if the data is usable, so daily checks are needed to verify this. The <a href="https://www.idealsvdr.com/" rel="nofollow">virtual data rooms</a> makes use of an email notification system to inform administrators of the status of the backups.Anonymoushttps://www.blogger.com/profile/14036616259587055782noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-31994022632542482242016-04-22T16:37:56.233+01:002016-04-22T16:37:56.233+01:00This is a good site , Thanks for the nice blog. ...This is a good site , Thanks for the nice blog. It was very useful for me. Keep sharing such ideas in the future as well. This was actually what I was looking for, and I am glad to came here! Thanks for sharing the such information with us. <br />Please check <a href="http://carmeans/best-car-vacuum" rel="nofollow"> Read me</a><br />HS Bloggerhttps://www.blogger.com/profile/05207190546352026444noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-50602609327685307832016-02-11T23:34:48.249+00:002016-02-11T23:34:48.249+00:00Looks like the short URLs generated for your feed ...Looks like the short URLs generated for your feed somehow are not working well. The Postgresql.org feed got a URL (http://postgr.es/p/3k%20P) instead of (http://postgr.es/p/3kP) ... i.e. an extra space ... that got converted to %20 in HTML parlance and thus, you probably aren't getting any traffic from postgresql.org from that feed (at least for that post).<br /><br />Just FYI.Anonymoushttps://www.blogger.com/profile/09660517959593093018noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-90883470795706633412015-07-03T06:34:35.305+01:002015-07-03T06:34:35.305+01:00yes, blogger is quite bad. I've in the to list...yes, blogger is quite bad. I've in the to list a proper website for this.The Doctorhttps://www.blogger.com/profile/18301101170664650551noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-61795643725615240282015-07-03T06:00:29.058+01:002015-07-03T06:00:29.058+01:00Oops, all the tabs were eaten before the post save...Oops, all the tabs were eaten before the post saved.:)Anonymoushttps://www.blogger.com/profile/14193254913146756361noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-69509244088371171562015-07-02T22:50:16.716+01:002015-07-02T22:50:16.716+01:00This is the reason why I like the pgadmin3's s...This is the reason why I like the pgadmin3's sql editor.<br />It's quick and efficient in sql development. Similar (without the drawback) to oracle's SQL*. <br /><br />I write hundreds of lines of sql (and plpgsql) code every day and with the approach described in this post I never get lost.The Doctorhttps://www.blogger.com/profile/18301101170664650551noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-28158815185233813042015-07-02T21:52:18.499+01:002015-07-02T21:52:18.499+01:00I agree that code formatting is a very important t...I agree that code formatting is a very important thing, but just imagine you type "select ... from ... where ..." a hundred times a day. Would it be easy for you to type all the keywords in uppercase? In fact, it is annoying and slowing down the performance of a developer.<br />The only reason I can think of doing that is that the sql is to be examined later by people who are not good at sql (such formatting makes the sql more understandable).<br /><br />It is hard to imagine so many carriage returns and tabs in a non-trivial sql. I mean, if there are more then 10 tables joined with subselects, functions' calls etc. the final select would be huge. I think, keeping a sql compact is more important (especially, if it is quite complex).<br /><br />For example:<br /><br />select t1.field1,<br /> t1.field2,<br /> t1.field3,<br /> t1.field4<br />from table1 t1<br /> join table2 t2 on t2.field1 = t1.field1<br /> join table3 t3 on t3.field1 = t1.field1<br /> left join table4 t4 on t4.field2 = t3.field2<br /> join table5 t5 on t5.field1 = t1.field1<br /> join table6 t6 on t6.field1 = t1.field1<br /> join table7 t7 on t7.field5 = t6.field5<br /> join table8 t8 on t8.field6 = t7.field6<br /> left join table9 t9 on t9.field12 = t1.field12<br />where t1.field3 = 30000<br /> and t1.field4 <> 1;<br />Anonymoushttps://www.blogger.com/profile/14193254913146756361noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-70988739831484919782013-01-02T14:06:47.000+00:002013-01-02T14:06:47.000+00:00Indeed a good planning can keep the vacuum full at...Indeed a good planning can keep the vacuum full at bay :)<br /><br />Unfortunately sometimes the space needed is simply too much and the space must be reclaimed with this command.<br /><br />What upset me was the lack of documentation about the behaviour not the behaviour itself.<br /><br />Merry Christmas and Happy New Year ;)Anonymoushttps://www.blogger.com/profile/02966919995930930023noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-89066495926710297492013-01-02T08:01:14.914+00:002013-01-02T08:01:14.914+00:00It certainly seems to me Fed, that you're sugg...It certainly seems to me Fed, that you're suggesting that the pg_cluster script is not the best way to manage any instances, after reading this, and knowing that damage that Kill -9 can cause, I am inclined to agree.<br /><br />Kill -9 is never a good thing on Postgres, although I have to admit, there have been times where I have had no choice but to -9 a runaway Postgres process, but in doing this, I kill -TERM all other processes first, minimizing the damage to shared mem. <br /><br />I now write/rewrite my own init scripts, even for RHEL. One cannot assume that they act the way you want them to, even with the scripts provided with source, and in the instance where an 'immediate' fails, I leave the process running and report out to allow a suitably armed DBA to fix the issue manually. <br /><br />On VACUUM FULL; I very rarely use this facility, simple as a hangover from earlier versions where VACUUM FULL was not like CLUSTER, and used to lock the tables for what seem liked forever (inefficiencies well known to most proficient DBA's). Setting more aggressive AUTOVACUUM settings, and using REINDEX where appropriate has always seemed to be enough for me. <br /><br />In an instance where disk space becomes an issue, that would be over to Sysadmins to correct, although if I as the DBA hadn't planned for enough space in the first instance, then I need to be shot for it! <br />Adding more spindles and new tablespaces on said spindles is usually the "get out" clause for a lack of space, as well as backing up and then removing old/redundant data. <br /><br />Obviously there is always the situation that hasn't been planned for, where an emergency VACUUM FULL is needed, but usually by that time, there is insufficient space on the server anyway. In that instance, you're up the creek already. Temporary NFS mounts anyone?<br /><br />In short, good planning (although not always possible) keeps the VACUUM FULL at bay!<br /><br />Merry Christmas, and a Happy New Year.Martin Frenchhttps://www.blogger.com/profile/15822244268226549820noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-77699664330692774502012-08-30T19:22:12.565+01:002012-08-30T19:22:12.565+01:00Great! You're the best!Great! You're the best!deftunixhttps://www.blogger.com/profile/07899072491803595348noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-76088008196879968192012-08-20T09:50:46.712+01:002012-08-20T09:50:46.712+01:00Using the implicit join give the query planner the...Using the implicit join give the query planner the freedom of choice.<br />Using the explicit join you can influence it as explained here<br /><br />http://www.postgresql.org/docs/9.1/static/explicit-joins.html<br /><br />I like the implicit notations because I feel the inner join more like a filter constraint, it's bad habit from my oracle experience where, before the 9i, no inner join or left outer join was allowed and the the (+) operator dominate the queries ;)<br />Anonymoushttps://www.blogger.com/profile/02966919995930930023noreply@blogger.comtag:blogger.com,1999:blog-164659665444159945.post-40553965953822864992012-08-20T09:44:26.547+01:002012-08-20T09:44:26.547+01:00Are there any technical benefits to using the impl...Are there any technical benefits to using the implicit join notation over explicit INNER JOIN e.g.<br /><br />SELECT<br /> productcode,<br /> noteid,<br /> datnot<br />FROM<br /> debitnoteshead AS hrd INNER JOIN <br /> debitnoteslines AS lns ON<br /> hdr.debnotid = lns.debnotid<br />WHERE<br /> hdr.datnot = lns.datnot AND<br /> lns.deblin > 1;<br />-- missing indentation due to comments formatting constraints.<br /><br />Thank you for your sharing the fruits of your experience.Anonymoushttps://www.blogger.com/profile/16703107900414842187noreply@blogger.com