segmentation fault when building postgres GiST index - postgresql

I'm using postgres 9.4 on Ubuntu 14.04 LTS.
When I execute this query:
create index a_idx on my_table using gist(my_column);
I'm getting error:
erver closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>
In the logs I can see this:
2016-04-21 11:30:11 BST LOG: server process (PID 7850) was terminated by signal 11: Segmentation fault
I checked if this column has any null values but it doesn't.
How can I debug this?
The structure of my_table is:
Table "public.my_table"
Column | Type | Modifiers | Storage | Stats target | Description
-----------+---------+-----------+----------+--------------+-------------
id | integer | not null | plain | |
my_column | bfp | | extended | |

Related

how this sample Forged digital certificate

I found a pe file,when i check digital certificate,i found winxp can identity the digital cert,but win10 can not,virus total also show that this file is not signd
Is this a fake digital cert?
how to made this happen?
winxp info:
enter image description here
win10 info
enter image description here
Windows XP used SHA1 hashes in the signatures, which is not supported on 10:
Source:
The following table shows which OS's support SHA-1 and SHA-256 code signatures:
+---------------------+-------------------------------+------------------------------+
| Windows OS | SHA-1 | SHA-256 |
+---------------------+-------------------------------+------------------------------+
| XP SP3, Server 2003 | Yes | No (need KB968730, KB938397) |
| Vista, Server 2008 | Yes | No (need KB2763674) |
| 7, Server 2008 R2 | No (if signed after 1/1/2016) | Yes (with latest updates) |
| 8.1, Server 2012 R2 | No (if signed after 1/1/2016) | Yes |
| 10, Server 2016 | No (if signed after 1/1/2016) | Yes |
+---------------------+-------------------------------+------------------------------+

Cannot run VSCode source code because its unable to find electron app in directory

Overview:
When I attempt to run VSCode with the instructions given in the contributions page to download all the packages, build the source code, and then run it all on the terminal, an error message pops up saying that I don't have the electron app in the vscode directory. Shouldn't have the electron app been installed when I ran the yarn command to install and build all the dependencies?
Steps to reproduce the bug:
$ yarn //building and installing all dependencies
$ yarn watchd //building vscode
$ ./scripts/code.sh //running vscode
Error Message:
Error launching app
Unable to find Electron app at /home/juan/Desktop/Projects/vscode
Cannot find module '/home/juan/Desktop/Projects/vscode/out/main'. Please verify that the package.json has a valid "main" entry
System Details:
CPUs | Intel(R) Core(TM) i7-6600U CPU # 2.60GHz (4 x 3200)
-- | --
GPU Status | 2d_canvas: unavailable_softwareflash_3d: disabled_softwareflash_stage3d: disabled_softwareflash_stage3d_baseline: disabled_softwaregpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwareviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: unavailable_softwarewebgl2: unavailable_software
Load (avg) | 1, 1, 1
Memory (System) | 7.63GB (0.12GB free)
Process Argv | . --no-sandbox
Screen Reader | no
VM | 0%
OS|Ubuntu 18.04 LTS
Extensions:
Extension | Author (truncated) | Version
-- | -- | --
Bookmarks | ale | 11.2.0
vscode-sqlite | ale | 0.8.2
code-gnu-global | aus | 0.2.2
npm-intellisense | chr | 1.3.0
vscode-svgviewer | css | 2.0.0
vscode-markdownlint | Dav | 0.36.0
jshint | dba | 0.10.21
vscode-eslint | dba | 2.1.5
vscode-html-css | ecm | 0.2.3
EditorConfig | Edi | 0.15.1
vscode-npm-script | eg2 | 0.3.12
vscode-firefox-debug | fir | 2.8.0
beautify | Hoo | 1.5.0
vscode-emacs-friendly | lfs | 0.9.0
rainbow-csv | mec | 1.7.0
python | ms- | 2020.5.80290
cpptools | ms- | 0.28.2
debugger-for-chrome | msj | 4.12.8
sqltools | mtx | 0.22.5
material-icon-theme | PKi | 4.1.0
rust | rus | 0.7.8
lc2k | vio | 1.1.1
Here is the bug report I filled in the vscode github page: https://github.com/microsoft/vscode/issues/99537
I got this same error myself when the code did not build correctly.
In your second step you do:
yarn watchd
I tried this command myself, but ran into the same issue that you have stated here. Although the official wiki suggests this as a tip, I would just ignore it.
Instead, do either of these instead (this is what the official wiki originally suggest to do):
Type: Ctrl + Shift + B
Or alternatively use the Command Palette:
Type: Ctrl + Shift + P
Search for the option called: Tasks: Run Build Task and select it.
Once you start the build task you'll see a couple of things:
Firstly, at the bottom of VS Code (on your status line), VS Code will let you know the code is building.
Secondly, The build command will open two terminals:
Task - Build VS Code
Task - Build VS Code Extensions
Watch the output for both of terminals, make sure:
Task - Build VS Code terminal outputs: [some time] Finished compilation ...
and
Task - Build VS Code Extensions terminal outputs: [some time] Finished compilation extensions ...
If not and the build fails, you'll probably get a notification from VS code saying so (You'll probably get the error twice, one for each task):
yarn ... exited with code [some non-zero integer]
A common error that may occur is the ENOSPC error from inotify (also documented well in a medium blog). You'll want to issue this command:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
Arch users would issue:
echo fs.inotify.max_user_watches=524288 | sudo tee /etc/sysctl.d/40-max-user-watches.conf && sudo sysctl --system
After fixing this, trying to build again should work. Start the build task again and make sure both tasks succeed. (You'll notice that the tasks do not end after they succeed. This is because they will watch for changes you make in the code while developing and automatically recompile for you).
If successful you may finally issue:
./scripts/code.sh
A new instance of VS Code should open called: Code - OSS dev. This is the version of VS Code you just built.

What actions done by thread will cause other threads and the whole process to terminate?

I was encountering bugs in my program which caused the whole process to terminate, while I debugged through my program and follow the Task Manager I could see my process terminated while running a certain thread.
I stepped through this thread and apparently I used exit() which caused the problem. I changed to pthread_exit() yet again I had the same issue, it turned out to be that the specific thread also had an illegal operation: division by zero.
pthread_exit
pthread_cancel
exit
illegal action
main thread return
When will those cause the process to terminate?
| | thread | process |
-----------------------------------------------------------------
| pthread_exit | finish | finish iff last running thread |
| pthread_cancel | finish | finish iff last running thread |
| exit() | finish | finish |
| Illegal operation | finish | finish |
| thread finishes | finish | finish iff last running thread |
| main thread finishes| finish | finish |
return is a wrapper function that contain exit sys_call, this is why the whole threads are terminated as well.
CPUs tend to throw an exception interrupt,
on things like division by zero, or dereferencing a NULL pointer. Causing the execution of the program to halt and return control to the OS to handle the event. The program may be terminated,
all resources freed depending on the OS.

Data corruption - ERROR: could not open segment 2 of relation

I am getting the below error for production database. I am new to PostgreSQL database. I need help to get the below error fixed.
2015-10-28 10:25:04,154 [monitor-thread-pool1-thread-6] ERROR [org.hibernate.util.JDBCExceptionReporter] ERROR: could not open segment 2 of relation 1663/98913/98947 (target block 427542): No such file or
directory
server1=> select oid::regclass from pg_class where relfilenode =98947;
oid
alert_instance_history
(1 row)
server1=> select oid::regclass from pg_class where relfilenode =98913;
oid
(0 rows)
server1=> select * from pg_database where oid=1663;
datname | datdba | encoding | datistemplate | datallowconn | datconnlimit | datlastsysoid | datvacuumxid | datfrozenxid | dattablespace | datconfig | datacl
---------+--------+----------+---------------+--------------+--------------+---------------+--------------+--------------+---------------+-----------+--------
(0 rows)
1. server1=> select version();
version
--------------------------------------------------------------------------------------------
PostgreSQL 8.1.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.5 (Debian 1:3.3.5-13)
(1 row)
Q1. Error says 2 relations but I can only find 98947, how i can check the other segment ?
Q2. I did just select on this table alert_instance_history, I can see records from this table. Do I need to check any thing else ?
server1=> select min(eventtimestamp) from alert_instance_history;
WARNING: could not write block 427542 of 1663/98913/98947 DETAIL:
Multiple failures --- write error may be permanent. ERROR: could not
open segment 2 of relation 1663/98913/98947 (target block 427542): No
such file or directory CONTEXT: writing block 427542 of relation
1663/98913/98947 server1=> server1=> reindex table
alert_instance_history; WARNING: could not write block 427542 of
1663/98913/98947 DETAIL: Multiple failures --- write error may be
permanent. ERROR: could not open segment 2 of relation
1663/98913/98947 (target block 427542): No such file or directory
CONTEXT: writing block 427542 of relation 1663/98913/98947
Q3. What's the posible option have to restore, Can I restore just one table ?
Backup of this database is done using pg_dump utility.

PostgreSQL Transaction ID went backwards

In PostgreSQL 9.0, I have a table that keeps tracks of last processed transactions. For some reason, it went backwards (in time)! Here is the table data:
seq_id | tx_id
628 | 10112
629 | 10118
630 | 10124
631 | 10130
632 | 10136
654 | 10160
655 | 10166 <---
656 | 4070 <---
657 | 4071
658 | 4084
659 | 4090
660 | 4096
How can this happen? Can a restart of the database induce such behavior?
Thanks for any hints.
Regards,
D.
This is an invalid issue. Please ignore.
It turns out that the issue came out of restoring the table from a backup and continue working with (invalid) previous data, in a newly created database :-(
Thanks you for all those who responded already.
Case closed.
Lesson learned: TXID will NOT go backwards and they do get synced to a slave instance if you're using a Master/Slave setup. TXID rollovers are also correctly handled. Hope this will help others who might be thinking TXID can go backwards!