id
related bits
0
processing priority
4
site type
3 (personal blog or private political site, e.g. Blogspot, Substack, also small blogs on own domains)
review version
11
html import
20 (imported)
first seen date
2024-11-03 17:11:16
expired found date
-
created at
2024-11-03 17:11:16
updated at
2026-03-11 15:28:47
length
22
crc
28355
tld
2211
nm parts
0
nm random digits
0
nm rare letters
0
is subdomain of id
13642151 (wordpress.com)
previous id
0
replaced with id
0
related id
-
dns primary id
0
dns alternative id
0
lifecycle status
0 (unclassified, or currently active)
deleted subdomains
0
page imported products
0
page imported random
0
page imported parking
0
count skipped due to recent timeouts on the same server IP
0
count content received but rejected due to 11-799
0
count dns errors
0
count cert errors
0
count timeouts
0
count http 429
0
count http 404
0
count http 403
0
count http 5xx
0
next operation date
-
server bits
—
server ip
-
mp import status
20
mp rejected date
-
mp saved date
-
mp size orig
397944
mp size raw text
104873
mp inner links count
41
mp inner links status
20 (imported)
title
🛩️ Shane Borden's Technology Blog
description
My Experiences Navigating Technology - All Views Are My Own
site name
🛩️ Shane Borden's Technology Blog
author
updated
2026-02-27 21:04:08
raw text
🛩️ Shane Borden's Technology Blog | My Experiences Navigating Technology – All Views Are My Own 🛩️ Shane Borden's Technology Blog My Experiences Navigating Technology – All Views Are My Own Menu Skip to content Home About Follow-Up: Reduce Vacuum by Using “ON CONFLICT” Directive Leave a reply I previously blogged about ensuring that the “ON CONFLICT” directive is used in order to avoid vacuum from having to do additional work. You can read the original blog here: Reduce Vacuum by Using “ON CONFLICT” Directive Now that Postgres has incorporated the “MERGE” functionality into Postgres 15 and above, I wanted to ensure that there was no “strange” behavior as it relates to vacuum when using merge. As you can see here, the “MERGE” functionality does perform exactly as expected. For example, when you attempt to have a merge where the directive is to try an insert first followed by an update, exactly one row is marked dead when the insert fails and the update succeeds...
redirect type
0 (-)
block type
0 (no issues)
detected language
1 (English)
category id
index version
1
spam phrases
0
text nonlatin
0
text cyrillic
0
text characters
65535
text words
14152
text unique words
1998
text lines
1937
text sentences
259
text paragraphs
199
text words per sentence
54
text matched phrases
0
text matched dictionaries
0
links self subdomains
0
links other subdomains
1 - docs.oracle.com
links other domains
links spam adult
0
links spam random
0
links spam expired
0
links ext activities
0
links ext ecommerce
0
links ext finance
0
links ext crypto
0
links ext booking
0
links ext news
0
links ext leaks
0
links ext ugc
33 - s0.wp.com, wp.me, s1.wp.com, twitter.com, linkedin.com, dbajonblog.wordpress.com, toomehforamemoir.wordpress.com, dbaspot.wordpress.com, wordpress.com
links ext klim
0
links ext generic
0
dol status
0
dol updated
2026-02-27 21:04:08
rss status
32 (unknown)
rss found date
2024-11-03 17:11:18
rss size orig
189255
rss items
10
rss spam phrases
0
rss detected language
1 (English)
inbefore feed id
-
inbefore status
0 (new)
sitemap path
sitemap status
40 (completed successful import of reports.txt file to table in_pages)
sitemap review version
2
sitemap urls count
44
sitemap urls adult
0
sitemap filtered products
1
sitemap filtered videos
0
sitemap found date
2024-11-03 17:11:17
sitemap process date
2025-03-26 11:48:34
sitemap first import date
-
sitemap last import date
2025-10-29 23:40:49