{"id":1753,"date":"2026-11-15T23:10:44","date_gmt":"2026-11-15T23:10:44","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=1753"},"modified":"2026-11-15T23:10:44","modified_gmt":"2026-11-15T23:10:44","slug":"postgresql-tuning-wizard-iis-php-manager","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/","title":{"rendered":"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">PostgreSQL will install and start on a 2 GB VPS without complaint, and it will quietly perform badly for months before anyone notices. The problem is almost never Postgres itself \u2014 it is that the default configuration assumes reading from local disks with abundant RAM and unlimited connections, which is the opposite of a small guest. This is a practical path from <code>apt install<\/code> to a tuned, pooled, observable instance, with the arithmetic behind each setting.<\/p>\n\n\n<!-- wp:heading level=\"2\" -->\n<h2>Install from the PGDG repository<\/h2>\n<!-- \/wp:post-content -->\n\n<!-- wp:paragraph -->\n<p>Distribution packages lag badly and some omit extensions you will want later. On Debian or Ubuntu, add the official repository so you get the current major version and a clean upgrade path:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>apt install -y curl ca-certificates gnupg lsb-release\ninstall -d \/usr\/share\/postgresql-common\/pgdg\ncurl -fsSL https:\/\/www.postgresql.org\/media\/keys\/ACCC4CF8.asc \\\n  -o \/usr\/share\/postgresql-common\/pgdg\/apt.postgresql.org.asc\necho \"deb [signed-by=\/usr\/share\/postgresql-common\/pgdg\/apt.postgresql.org.asc] \\\n  https:\/\/apt.postgresql.org\/pub\/repos\/apt $(lsb_release -cs)-pgdg main\" \\\n  &gt; \/etc\/apt\/sources.list.d\/pgdg.list\napt update &amp;&amp; apt install -y postgresql-16 postgresql-contrib-16 pgbouncer\nsystemctl status postgresql@16-main --no-pager<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Keep configuration in a drop-in rather than editing <code>postgresql.conf<\/code> directly. Upgrades rewrite the main file, and a drop-in survives them, which makes it obvious later which settings you chose and why.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>Memory math for a 2\u20134 GB guest<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Three settings determine almost all of Postgres&#8217;s memory behaviour, and they interact. <code>shared_buffers<\/code> is pre-allocated shared memory and is fixed at startup. <code>work_mem<\/code> is allocated per sort or hash node per query, so the real cost is <code>work_mem \u00d7 concurrent nodes<\/code>. <code>effective_cache_size<\/code> allocates nothing \u2014 it tells the planner how much OS-level caching to assume and therefore how eagerly to use indexes.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:table -->\n<figure class=\"wp-block-table\"><table><thead><tr><th>Setting<\/th><th>2 GB guest<\/th><th>4 GB guest<\/th><th>Reasoning<\/th><\/tr><\/thead><tbody><tr><td>shared_buffers<\/td><td>256 MB<\/td><td>512 MB<\/td><td>~12\u201315% of RAM, not 25%<\/td><\/tr><tr><td>work_mem<\/td><td>4 MB<\/td><td>8 MB<\/td><td>Multiplied per sort node, per connection<\/td><\/tr><tr><td>maintenance_work_mem<\/td><td>64 MB<\/td><td>128 MB<\/td><td>Affects VACUUM and index builds<\/td><\/tr><tr><td>effective_cache_size<\/td><td>1 GB<\/td><td>2.5 GB<\/td><td>Planner hint, no allocation<\/td><\/tr><tr><td>max_connections<\/td><td>40<\/td><td>80<\/td><td>Low because a pooler sits in front<\/td><\/tr><tr><td>wal_buffers<\/td><td>16 MB<\/td><td>16 MB<\/td><td>Diminishing returns above this<\/td><\/tr><\/tbody><\/table><\/figure>\n<!-- \/wp:table -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code># \/etc\/postgresql\/16\/main\/conf.d\/20-small-vps.conf\nshared_buffers = 256MB\nwork_mem = 4MB\nmaintenance_work_mem = 64MB\neffective_cache_size = 1GB\nmax_connections = 40\nwal_compression = on\nrandom_page_cost = 1.1\neffective_io_concurrency = 200\ncheckpoint_timeout = 15min\nmax_wal_size = 1GB<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p><code>random_page_cost = 1.1<\/code> matters more than most people realise. The default of 4.0 assumes spinning disks; on NVMe-backed VPS storage, keeping it at 4.0 makes the planner avoid indexes and choose sequential scans that read far more data than necessary. If your provider gives you network-attached storage rather than local NVMe, start at 1.5 instead and measure.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>pgbouncer: fewer backends, more throughput<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Each Postgres backend process has meaningful per-process memory overhead \u2014 a few megabytes each even when idle \u2014 and the cost of forking one per web request is brutal on a small guest. pgbouncer in transaction mode keeps a small fixed set of server connections and multiplexes thousands of client connections over them.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>; \/etc\/pgbouncer\/pgbouncer.ini\n[databases]\nappdb = host=127.0.0.1 port=5432 dbname=appdb\n\n[pgbouncer]\nlisten_addr = 127.0.0.1\nlisten_port = 6432\nauth_type = scram-sha-256\nauth_file = \/etc\/pgbouncer\/userlist.txt\npool_mode = transaction\nmax_client_conn = 500\ndefault_pool_size = 20\nmin_pool_size = 5\nreserve_pool_size = 5\nserver_idle_timeout = 60\nquery_wait_timeout = 10<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Transaction mode is the right default for web applications, with one hard constraint: it rules out session-level features, including <code>SET<\/code> statements that persist beyond a transaction, advisory locks held across requests, and prepared statements in some client libraries. Laravel, Django and Rails all work in transaction mode; some ORMs need prepared-statement caching disabled or a <code>pool_mode = session<\/code> exception for specific users.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>Autovacuum on a low-IOPS disk<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Provider block storage often delivers a few hundred IOPS, and aggressive autovacuum on a table with a large index can saturate that for minutes. The fix is not to disable autovacuum \u2014 disabled autovacuum leads to transaction ID wraparound, which stops the database entirely \u2014 but to slow it down and give it a bigger cost budget so it does fewer, larger passes:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>autovacuum_max_workers = 2\nautovacuum_naptime = 30s\nautovacuum_vacuum_cost_limit = 400\nautovacuum_vacuum_cost_delay = 5ms\nautovacuum_vacuum_scale_factor = 0.05\nautovacuum_analyze_scale_factor = 0.02<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Lowering <code>scale_factor<\/code> to 0.05 makes autovacuum trigger on tables far earlier than the default 20% dead-tuple threshold, which matters on small tables that churn heavily. Verify with <code>SELECT relname, n_dead_tup, last_autovacuum FROM pg_stat_user_tables ORDER BY n_dead_tup DESC LIMIT 10;<\/code> \u2014 if <code>n_dead_tup<\/code> grows steadily for a table without any autovacuum timestamp, something is blocking it.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>Connecting a PHP application over PDO<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>The application changes are small: point the host at port 6432 instead of 5432, and make sure the connection is not held open longer than a request. In PDO, disable persistent connections when using a transaction pooler \u2014 persistent client connections defeat the point of pooling.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>\/\/ config\/database.php (Laravel-style, PDO underneath)\n'pgsql' =&gt; [\n    'driver'   =&gt; 'pgsql',\n    'host'     =&gt; '127.0.0.1',\n    'port'     =&gt; '6432',\n    'database' =&gt; 'appdb',\n    'username' =&gt; 'appuser',\n    'password' =&gt; getenv('DB_PASSWORD'),\n    'options'  =&gt; [\n        PDO::ATTR_PERSISTENT =&gt; false,\n        PDO::ATTR_EMULATE_PREPARES =&gt; false,\n    ],\n],<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Also set <code>options=-c statement_timeout=30000<\/code> in the DSN so a runaway web request cannot hold a pooled server connection for minutes. On a pool of 20 that single setting prevents the classic cascading failure where three slow queries block the entire application.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>Measuring with pg_stat_statements<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Without measurement you are guessing. <code>pg_stat_statements<\/code> aggregates query cost across executions and is the single most useful extension on a shared instance. It requires a shared preload, so edit the config and restart once:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>shared_preload_libraries = 'pg_stat_statements'\npg_stat_statements.max = 5000\npg_stat_statements.track = top\n\n-- after restart:\nCREATE EXTENSION IF NOT EXISTS pg_stat_statements;\nSELECT pg_stat_statements_reset();\n\n-- top 10 queries by total time\nSELECT round(total_exec_time::numeric,1) AS ms,\n       calls,\n       round(mean_exec_time::numeric,2) AS mean_ms,\n       rows,\n       left(query, 90) AS query\nFROM pg_stat_statements\nORDER BY total_exec_time DESC\nLIMIT 10;<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Read the output in two passes. Sort by <code>total_exec_time<\/code> to find what is costing you most overall, then sort by <code>mean_exec_time<\/code> with a <code>calls &gt; 100<\/code> filter to find the individual queries that are slow every time. The first list is usually a handful of reports; the second is usually a missing index.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>Maintenance tasks and safe defaults<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Two cron-style jobs are worth enabling on any small instance. Autovacuum handles dead tuples, but it does not update planner statistics aggressively enough for tables that bulk-load, and it does not handle bloat from rolled-back transactions. A weekly <code>ANALYZE<\/code> on the application schema and a monthly check for tables where dead tuples exceed live ones catch most of it:<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>-- tables with the worst bloat ratio\nSELECT relname, n_live_tup, n_dead_tup,\n       round(100.0*n_dead_tup\/nullif(n_live_tup,0),1) AS dead_pct\nFROM pg_stat_user_tables\nWHERE n_live_tup &gt; 1000\nORDER BY dead_pct DESC NULLS LAST\nLIMIT 10;\n\n-- refresh statistics on a schema after bulk loads\nANALYZE VERBOSE public;<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Also check that <code>log_min_duration_statement<\/code> is set to something useful \u2014 500 ms is a reasonable starting point on a small guest \u2014 and that the log lives somewhere rotated. A long-running query log is often the fastest path to the query that is making the whole instance feel slow, especially when <code>pg_stat_statements<\/code> has been reset by a restart.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:heading level=\"2\" -->\n<h2>Indexing and cache hit ratio checks<\/h2>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Two numbers tell you whether the tuning worked. Buffer cache hit ratio above 99% for an OLTP workload means the working set fits; below 95% means either <code>shared_buffers<\/code> is too small or the query pattern reads far too much data. Index usage below 90% suggests indexes are missing or the planner is choosing sequential scans.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:code -->\n<pre class=\"wp-block-code\"><code>SELECT round(100.0 * sum(blks_hit) \/ nullif(sum(blks_hit+blks_read),0), 2)\n       AS cache_hit_pct FROM pg_stat_database;\n\nSELECT relname, seq_scan, idx_scan,\n       round(100.0 * idx_scan \/ nullif(seq_scan + idx_scan,0), 1) AS idx_pct\nFROM pg_stat_user_tables\nORDER BY seq_scan DESC LIMIT 10;<\/code><\/pre>\n<!-- \/wp:code -->\n\n<!-- wp:paragraph -->\n<p>Reset statistics after any configuration change so you are comparing like with like, and re-check a day later rather than an hour later. A small VPS serves a small working set, so most tuning wins come from fixing one bad query rather than from adjusting a knob. If the hit ratio stays poor after that work and <code>MemAvailable<\/code> is routinely low, the honest answer is more RAM \u2014 the <a href=\"https:\/\/virtualserversvps.com\/\">VirtualServersVPS<\/a> plan tiers are sized so that a 4 GB guest covers a typical small application with room for the OS page cache Postgres relies on.<\/p>\n<!-- \/wp:paragraph -->\n","protected":false},"excerpt":{"rendered":"<p>PostgreSQL will install and start on a 2 GB VPS without complaint, and it will quietly perform badly for months before anyone notices. The problem is almost never Postgres itself&#8230;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[3],"tags":[],"class_list":["post-1753","post","type-post","status-publish","format-standard","hentry","category-performance-optimization"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console - Virtual Servers VPS Blog<\/title>\n<meta name=\"description\" content=\"PostgreSQL will install and start on a 2 GB VPS without complaint, and it will quietly perform badly for months before anyone notices. The problem is\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console\" \/>\n<meta property=\"og:description\" content=\"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual Servers VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-15T23:10:44+00:00\" \/>\n<meta name=\"author\" content=\"Virtual-Servers-Vps-Editor\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Virtual-Servers-Vps-Editor\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/\",\"name\":\"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console - Virtual Servers VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\"},\"datePublished\":\"2026-11-15T23:10:44+00:00\",\"author\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\"},\"description\":\"PostgreSQL will install and start on a 2 GB VPS without complaint, and it will quietly perform badly for months before anyone notices. The problem is\",\"breadcrumb\":{\"@id\":\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtualserversvps.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#website\",\"url\":\"https:\/\/virtualserversvps.com\/blog\/\",\"name\":\"Virtual Servers VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0\",\"name\":\"Virtual-Servers-Vps-Editor\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g\",\"caption\":\"Virtual-Servers-Vps-Editor\"},\"sameAs\":[\"https:\/\/virtualserversvps.com\/blog\"],\"url\":\"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console - Virtual Servers VPS Blog","description":"PostgreSQL will install and start on a 2 GB VPS without complaint, and it will quietly perform badly for months before anyone notices. The problem is","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/","og_locale":"en_US","og_type":"article","og_title":"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console","og_description":"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console","og_url":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/","og_site_name":"Virtual Servers VPS Blog","article_published_time":"2026-11-15T23:10:44+00:00","author":"Virtual-Servers-Vps-Editor","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Virtual-Servers-Vps-Editor","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/","url":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/","name":"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console - Virtual Servers VPS Blog","isPartOf":{"@id":"https:\/\/virtualserversvps.com\/blog\/#website"},"datePublished":"2026-11-15T23:10:44+00:00","author":{"@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0"},"description":"PostgreSQL will install and start on a 2 GB VPS without complaint, and it will quietly perform badly for months before anyone notices. The problem is","breadcrumb":{"@id":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/virtualserversvps.com\/blog\/postgresql-tuning-wizard-iis-php-manager\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtualserversvps.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Installing PostgreSQL on a Small VPS: Tuning a pg pooler Without a Managed Console"}]},{"@type":"WebSite","@id":"https:\/\/virtualserversvps.com\/blog\/#website","url":"https:\/\/virtualserversvps.com\/blog\/","name":"Virtual Servers VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtualserversvps.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/82a299a8284a66ff49f97c74684724a0","name":"Virtual-Servers-Vps-Editor","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtualserversvps.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d820b15f1cd028e97610d9adf536df7be5cb6423869967037d468d5355fa003f?s=96&d=mm&r=g","caption":"Virtual-Servers-Vps-Editor"},"sameAs":["https:\/\/virtualserversvps.com\/blog"],"url":"https:\/\/virtualserversvps.com\/blog\/author\/virtualserversvps\/"}]}},"_links":{"self":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1753","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/comments?post=1753"}],"version-history":[{"count":1,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1753\/revisions"}],"predecessor-version":[{"id":1756,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/posts\/1753\/revisions\/1756"}],"wp:attachment":[{"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/media?parent=1753"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/categories?post=1753"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtualserversvps.com\/blog\/wp-json\/wp\/v2\/tags?post=1753"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}