Hackorum
Menu
Theme
Topics
Search
Statistics
Reports
Help
Sign in
Register
PostgreSQL Hackers Archive
Topics
Search
Reports
Sign in
Register
Statistics
Help
Sign in
Register
Filter:
Started threads
Replied (own)
Replied (other)
Sent first patch
Sent follow-up patch
Activity
2026
2025
2024
2023
2022
2021
2020
2019
2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008
2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Wk
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
Mon
Tue
Wed
Thu
Fri
Sat
Sun
Messages on August 16, 2019
Threads
18
messages
7
Started
2
Replied in own
9
Replied to others
in 8 threads
Patches
none in this period
0
New patch
first in its thread
0
Follow-up
revision of an earlier one
Activity
Thread
Sent
Replied (other)
allocation limit for encoding conversion
almost 7 years ago
Replied (other)
UNION ALL
almost 7 years ago
Replied (own)
pgsql: Fix plpgsql to re-look-up composite type names at need.
almost 7 years ago
Replied (other)
slow queries on system tables
almost 7 years ago
Replied (other)
Bad Estimate for complex query with JOINS on subselects and OR in where conditions
almost 7 years ago
Replied (own)
Unexpected "shared memory block is still in use"
almost 7 years ago
Replied (other)
Bad Estimate for complex query with JOINS on subselects and OR in where conditions
almost 7 years ago
Replied (other)
Wrong drop procedure example
almost 7 years ago
Replied (other)
length of string containing blanks is 0, || behaves differently than concat on string of blanks
almost 7 years ago
Replied (other)
Error XX000 After pg11 upgrade
almost 7 years ago
Replied (other)
Segmentation fault during update inside ExecBRUpdateTriggers
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago
Started thread
pgsql: Prevent possible double-free when update trigger returns old tup
almost 7 years ago