REGEXVAULTv2.0
Dev & Systems/Shell
Verified Safe

Process ID (PID) Regex for Go

/^(?:[1-9][0-9]{0,5}|[1-3][0-9]{6}|4194304)$/

What this pattern does

This page provides a well-structured, multi-part regular expression for matching process id (pid), ported and verified for Go. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

Go
// Process ID (PID)
// ReDoS-safe | RegexVault — Dev & Systems > Shell

package validation

import "regexp"

var processIdPidRe = regexp.MustCompile(`^(?:[1-9][0-9]{0,5}|[1-3][0-9]{6}|4194304)$`)

func ValidateProcessIdPid(s string) bool {
    return processIdPidRe.MatchString(s)
}

// Example
// fmt.Println(ValidateProcessIdPid("1")) // true

Test Cases

Matches (Valid)
Rejects (Invalid)
10
12344194305
99999-1
4194304abc
6553612.34

When to use this pattern

This pattern is drawn from the Dev & Systems > Shell category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

PID recycling is immediate — a PID captured at one moment may refer to a different process moments later. Never rely on PID alone for security decisions.

Technical Notes

PID 1 is always init/systemd. Linux defaults to max PID 32768 (/proc/sys/kernel/pid_max), configurable up to 4194304 (2^22). PID 0 is not a valid kill/signal target.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern